Julia: Workflow Tips, and What is New in v1.9 | 2nd DigiWell Julia Seminar 2023

[@raju-bitter]

Fantastic presentation, and extremely valuable info. Much appreciated!

[@YinZhu]

This is so great! Our team used Julia two years ago, we got a good workflow by then. Recently we are considering to using Julia again for a new project and this video gives us a great update on the new stuff in recent two years.

[@NickWindham]

Great video! Simple pro tips like revise overcome peoples’ outdated objections to Julia.

[@enderw88]

I am very new to Julia. Going through these “well known” items just saved me months!

[@NickWindham]

SAME

[@Examantel]

24:31 What is new in 1.9

[@Daniel_Zhu_a6f]

i'm not sure how revise helps in practice, but i guess i just have a different workflow. Cthulu one sounds so cool though, definitely worth looking into

[@halneufmille]

Great demo. 13:30 I'm wondering how hard would it be to actually detect that the empty list [] is initialized with type any, but later filled with only Float64 types? The user could be warned: "By the way, you may want to use Float64[] directly.", maybe in a similar way in which the syntax "1:length(x)" is discouraged.

[@volkeredelmann7619]

Could you please provide the link to the slides?

[@hispekness180]

Is version 1.9 out?

[@gregandark8571]

@Kushal Gaikwad The native compilation is planned for which version of Julia?

[@chrisrackauckasofficial]

@@gregandark8571 v1.9, which should come out in the next month or so.

[@gregandark8571]

@@chrisrackauckasofficial And what about the size ? As always 150Mb for typical Hello world? or this time something is really gonna change?

[@chrisrackauckasofficial]

@@gregandark8571 it's already changing. In v1.9 the REPL and metadata is able to be removed from the build which cuts out a big portion. Then there's some near future (v1.10/v1.11) pieces that will do a lot more too. It's been identified that one of the main reasons for the large image size is actually just that the zipping changes symlinks to copies, which means it's fairly simple to cut down another chunk. Another big piece is the moving out of SparseArrays from Base so that one could build images without SuiteSparse. So at least a lot of the main contributors have been identified and are being tackled one-by-one.

[@gregandark8571]

@@chrisrackauckasofficial Awesome,thanks you very much!

[@SkyFly19853]

Wow...

[@djangoworldwide7925]

Basically you make it more and more similar to R/Python. That's actually great

[@splat752]

@craig earls: really? Did you enter a parallel universe and try both paths?

[@enderw88]

I typically A/B test all aspects of my life. Doesn’t everybody?

[@NickWindham]

@@enderw88 😂