5 ms·

That' s solved more than 1 year ago https://news.ycombinator.com/item?id=38783886 https://news.ycombinator.com/item?id=38783886 https://modernjuliaworkflows.org

by xgdgsc 1y ago

That' s solved more than 1 year ago https://news.ycombinator.com/item?id=38783886 https://news.ycombinator.com/item?id=38783886 https://modernjuliaworkflows.org/optimizing/#compilation https://modernjuliaworkflows.org/optimizing/#compilation .

aragilar 1y ago
Are you actually sure it's solved? I note that Julia proponents have a history of claiming that an issue has been solved when it is apparent that it has not been solved (see e.g. https://danluu.com/julialang/ https://danluu.com/julialang/).
- xgdgsc 1y ago
  Yes. I don' t know why you' d rather trust an article from 10 years ago to understand current status.
- electroly 1y ago
  The events of my post happened in the last two months on Julia version 1.11.5, and this poster simply linked to a primer on PackageCompiler.jl which is the thing I said I was using in my post. It's not solved; at best there are complicated mitigations that let you control when the long compilation happens without avoiding it. If you try out Julia, you will run into the issue, and as a first-time user you won't be prepared to implement the mitigations, none of which are suitable for ad hoc usage. The sysimage only works for us because we rarely change our packages so we can build it ahead of time in GitHub Actions.
  - xgdgsc 1y ago
    The tradeoff between compilation time and programmer productivity and running speed is worth it compared with using any other language. You should consider most users don' t need to build an image . They just do things in the REPL with Revise.jl (which is fast). Or use a bit of PrecompileTools.jl to get good enough startup time (which isn' t complicated if you are the code writer). Package compiling works even large and slow is a bonus. https://pypl.github.io/PYPL.html https://pypl.github.io/PYPL.html Julia still grows despite all those controversial articles for a reason.

by xgdgsc 1y ago

aragilar 1y ago

Are you actually sure it's solved? I note that Julia proponents have a history of claiming that an issue has been solved when it is apparent that it has not been solved (see e.g. https://danluu.com/julialang/ https://danluu.com/julialang/).

xgdgsc 1y ago
Yes. I don' t know why you' d rather trust an article from 10 years ago to understand current status.
electroly 1y ago
The events of my post happened in the last two months on Julia version 1.11.5, and this poster simply linked to a primer on PackageCompiler.jl which is the thing I said I was using in my post. It's not solved; at best there are complicated mitigations that let you control when the long compilation happens without avoiding it. If you try out Julia, you will run into the issue, and as a first-time user you won't be prepared to implement the mitigations, none of which are suitable for ad hoc usage. The sysimage only works for us because we rarely change our packages so we can build it ahead of time in GitHub Actions.
- xgdgsc 1y ago
  The tradeoff between compilation time and programmer productivity and running speed is worth it compared with using any other language. You should consider most users don' t need to build an image . They just do things in the REPL with Revise.jl (which is fast). Or use a bit of PrecompileTools.jl to get good enough startup time (which isn' t complicated if you are the code writer). Package compiling works even large and slow is a bonus. https://pypl.github.io/PYPL.html https://pypl.github.io/PYPL.html Julia still grows despite all those controversial articles for a reason.