Live data from Hacker News

Julia 1.6 Highlights

julialang.org

11–20 of 224 posts

Re: Julia 1.6 Highlights

#11
post #9

Is there a per-project way to manage dependencies yet? I find global package installation to be the biggest weakness of all the R projects out there. Anaconda can help, but it’s not widely used for R projects. And Docker... well, don’t get me started.

Yeah. Julia's had that since (at least) 1.0. Environments are built-in, and you specify project dependencies in a Projects.toml file https://pkgdocs.julialang.org/v1/toml-files/.

Re: Julia 1.6 Highlights

#12
post #9

Is there a per-project way to manage dependencies yet? I find global package installation to be the biggest weakness of all the R projects out there. Anaconda can help, but it’s not widely used for R projects. And Docker... well, don’t get me started.

I might be misunderstanding your question, but this post is about Julia, not R. Julia has a pretty great per-project dependency management.

Re: Julia 1.6 Highlights

#13
post #9

Is there a per-project way to manage dependencies yet? I find global package installation to be the biggest weakness of all the R projects out there. Anaconda can help, but it’s not widely used for R projects. And Docker... well, don’t get me started.

renv is how R projects do per-package dependency management. Before renv there was packrat. This has been a solved problem for years now...

Re: Julia 1.6 Highlights

#14
I've been running the 1.6 release candidates, and the compilation speed improvements have been massive. There have been plenty of instances in the past where I've tried to 'quickly' show off some Julia code, and I end up waiting ~45 seconds for a plot to show or a minute for a Pluto notebook to run, and that's not to mention waiting for my imports to finish. It's still slower than Matlab for the first run, but it's at least in the same ballpark now.

Re: Julia 1.6 Highlights

#15
post #5

Cool, I was thinking of downloading the RC, the demo was so impressive. Will there be an M1 Mac version for 1.7?

I think so - Julia master branch (1.7 precursor) works on M1, but not all the dependencies that some packages require have been built for M1. Though, I understand that the wonderful packaging system and the folks who work on it are working on it. > `git clone https://github.com/JuliaLang/julia ` and `make` should be enough at this point. https://github.com/JuliaLang/julia/issues/36617#issuecomment...

Cool, I'll start with 1.6, but it looks interesting of course :)

Re: Julia 1.6 Highlights

#16
Whatever improves loading times is more than welcome. It's not really acceptable to wait because you import some libraries. In understand Julia makes lots of things under the hood and that there's a price to pay for that but being a python user, it's a bit inconvenient.

But I'll sure give it a try because Julia hits a sweet spot between expressiveness and speed (at least for the kind of stuff I do : matrix, algorithms, graphs computations).

Re: Julia 1.6 Highlights

#17
maybe i misread this, but milestone "1.6 blockers" still has 3 open with "1.6 now considered feature-complete. This milestone tracks release-blocking issues." - so how can 1.6 be ready?

Re: Julia 1.6 Highlights

#18
post #9

Is there a per-project way to manage dependencies yet? I find global package installation to be the biggest weakness of all the R projects out there. Anaconda can help, but it’s not widely used for R projects. And Docker... well, don’t get me started.

Yeah. Julia's had that since (at least) 1.0. Environments are built-in, and you specify project dependencies in a Projects.toml file https://pkgdocs.julialang.org/v1/toml-files/ .

Small nitpick; its Project.toml (or JuliaProject.toml, to avoid name clashes) not Projects.toml

Re: Julia 1.6 Highlights

#19

maybe i misread this, but milestone "1.6 blockers" still has 3 open with "1.6 now considered feature-complete. This milestone tracks release-blocking issues." - so how can 1.6 be ready?

It is simple. Those issues shouldn't have had the milestone.

Re: Julia 1.6 Highlights

#20

maybe i misread this, but milestone "1.6 blockers" still has 3 open with "1.6 now considered feature-complete. This milestone tracks release-blocking issues." - so how can 1.6 be ready?

It is simple. Those issues shouldn't have had the milestone.

I see. But you should work on your release process if thing like this happen.
Post reply on HN