Live data from Hacker News

Julia 1.10

docs.julialang.org

11–20 of 104 posts

Re: Julia 1.10

#11

Earlier quoted context omitted.

You don't need Julia. Julia was trying to be a better python. We will have better python in form of Mojo.

Mojo is vapourware from a private company (and we all know how those turn out re programming languages) until proven otherwise.

What other private company languages are there? Swift is the best example I can think of, which matches Mojo's situation down to the head of the project.

Re: Julia 1.10

#12
post #9

I like R and used it two ways. 1) Scheme-like functionalish 2) Tiddyverse and found Julia to be a lot of talk but seemed clunky to me.

btw, there has been a pretty nice effort of reimplementing the tidyverse in julia with https://github.com/TidierOrg/Tidier.jl and it seems to be quite nice to work with, if you were missing that from R at least

Re: Julia 1.10

#13

Im not sure if Julia will ever take off. Right now there are huge investments in the AI space and Julia has no presence in those.

As much as it pains me to say it, I don't think Julia will. It looks to me like the practical problems with Julia, while addressable, are being addressed too slowly. There is simply too many rough edges and usability problems as it is now, and at the current pace it will take maybe 10 or 15 years to address them. On the other hand, the major use case for Julia is to have a fast, dynamic language. And it seems to me t…

What's wrong with JS/TS or Lua as a fast dynamic language?

Re: Julia 1.10

#14

Im not sure if Julia will ever take off. Right now there are huge investments in the AI space and Julia has no presence in those.

It has already taken off and found its not so small niche. I don't think it will ever be one of the "big 10" languages (by users), but it has already a _big_ user base.

Re: Julia 1.10

#15
post #13

Earlier quoted context omitted.

As much as it pains me to say it, I don't think Julia will. It looks to me like the practical problems with Julia, while addressable, are being addressed too slowly. There is simply too many rough edges and usability problems as it is now, and at the current pace it will take maybe 10 or 15 years to address them. On the other hand, the major use case for Julia is to have a fast, dynamic language. And it seems to me t…

What's wrong with JS/TS or Lua as a fast dynamic language?

Javascript doesn't compile to native code, so isn't as fast. I've never tried LuaJIT, though, that's supposed to be on par with Julia.

Re: Julia 1.10

#16

Earlier quoted context omitted.

scientific models and simulations can be and are made very successfully in julia. In particular the diffeq landscape is probably the languages largest comparative advantage

That’s a broad area. I work in astrodynamic simulations, and don’t know anyone doing much work in Julia. Maybe a couple of grad students playing with it, but that’s it. 99% of the work is Python, Fortran, and C/C++. Are there subdomains that use it a lot? I am not sure what the diffeq landscape is exactly although it sounds related to dynamical simulations?

I'm sure there are other subdomains that make use of Julia, but in particular I think if your problem involves writing an evolution-like or agent-based-model-like simulation you may find the strengths of Julia particularly compelling

Re: Julia 1.10

#17
post #11

Earlier quoted context omitted.

Mojo is vapourware from a private company (and we all know how those turn out re programming languages) until proven otherwise.

What other private company languages are there? Swift is the best example I can think of, which matches Mojo's situation down to the head of the project.

IBM has some, ABAP, ...

Re: Julia 1.10

#18
I used Julia to build a macroeconomic model (DSGE-VAR) during my econ studies. I liked the conceptual decisions and the language per se (ie as a spec), but DX was quite bad: low discoverability of features and proper typings, clunky metaprogramming, long compilation times, impossibility of struct redefinitions in REPL. My interest died pretty fast because of it.

Re: Julia 1.10

#19
post #13

Earlier quoted context omitted.

What's wrong with JS/TS or Lua as a fast dynamic language?

Javascript doesn't compile to native code, so isn't as fast. I've never tried LuaJIT, though, that's supposed to be on par with Julia.

> Javascript doesn't compile to native code, so isn't as fast.

There are AOT compilers for JS.

Re: Julia 1.10

#20
The load time improvements are amazing. Thanks to everyone that was involved. I've been using it locally for months now simply because of this feature and I had to update my "how to deal with compile-time" blog post (https://sciml.ai/news/2022/09/21/compile_time/) to basically say system images really aren't needed anymore with these improvements. With that and the improvements to parallel compilation I tend to not care about "first time to X" anymore. To me it's solved and I'm onto other things (though I personally need to decrease the precompilation time of DifferentialEquations.jl, but all of the tools exist in v1.10 and that's on me to do, ya'll have done your part!).

Additionally:

* Parser error messages are clearer

* Stack traces are no longer infinitely long! They are good and legible!

* VS Code auto-complete stuff is snappier and more predictive (might be unrelated, but is a recent improvement in some VS Code things)

Altogether, I'm pretty happy with how this one shaped up and am looking forward to static compilation and interfaces being the next big focus areas.

Post reply on HN