I'm glad this is getting attention. The fact that a minimal example using some larger packages, like Plots, easily exceeds a gigabyte is ridiculous but it's good to understand why. If Julia could produce more reasonable binaries, it would really be perfect for me. Everything else about the language hits the spot for me.
00:00 - intro 00:21 - The function we'll compile with package compiler 01:23 - Fora function that just does addition, the size is 901 MB (with Julia 1.6 based PkgCompiler) 02:43 - Quick aside, sometimes binaries are just big cause they include a lot of things (hint hint, our binary has a lot too) 04:00 - Specialization means big binaries 05:23 - Exactly why is our package (sys image) so big? 06:42 - Shrink ray time 11:22 - Summary of our journey to get to 50MB from 900 16:14 - The guide on how to shrink your thingamajig the same way 17:21 - What's left in our sys image? 18:46 - The Julia base library is kinda big 20:45 - Nobody like reflection (ok, actually, this segment is that reflection makes inspection difficult) 23:23 - Roadmap 28:10 - That's it for the slides 28:30 Q&A starts and I'm too lazy to segment them
This is the most compelling reason I see for Julia 2.0. Shrink Base. Refactor it to minimize the core language, and put other features in packages. It would also help with maintainability and technical debt. I hope eventually we get there. May take several years, though.
![Seungmin "그렇게, 천천히, 우리(As we are)" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/kAzmhLHePqU/mqdefault.jpg)
I'm glad this is getting attention. The fact that a minimal example using some larger packages, like Plots, easily exceeds a gigabyte is ridiculous but it's good to understand why. If Julia could produce more reasonable binaries, it would really be perfect for me. Everything else about the language hits the spot for me.
00:00 - intro
00:21 - The function we'll compile with package compiler
01:23 - Fora function that just does addition, the size is 901 MB (with Julia 1.6 based PkgCompiler)
02:43 - Quick aside, sometimes binaries are just big cause they include a lot of things (hint hint, our binary has a lot too)
04:00 - Specialization means big binaries
05:23 - Exactly why is our package (sys image) so big?
06:42 - Shrink ray time
11:22 - Summary of our journey to get to 50MB from 900
16:14 - The guide on how to shrink your thingamajig the same way
17:21 - What's left in our sys image?
18:46 - The Julia base library is kinda big
20:45 - Nobody like reflection (ok, actually, this segment is that reflection makes inspection difficult)
23:23 - Roadmap
28:10 - That's it for the slides
28:30 Q&A starts and I'm too lazy to segment them
Thank you. We tweak your timestamps a bit and add the to the video description.
@@gregandark8571 To qute Jeff Bezanson "Yikes!".
I always enjoy Jeff Bezanson's talks.
This is the most compelling reason I see for Julia 2.0. Shrink Base. Refactor it to minimize the core language, and put other features in packages. It would also help with maintainability and technical debt. I hope eventually we get there. May take several years, though.
+/- how much?
I mean - In how many years do you think we'll get Julia 2.0 with all the native compilation candy's?
Great talk! Can you please detail how to remove LLVM from the geneerated lib ?
OK, I just realized it's just deleting it from the lib directory... 🤦
If nothing useful is exported from the toy example, shouldn't the compiler just be able to make it all a noop?
21:50 😂
so you went from "omg, that's bananas!" to "oh nelly, that's bloated!"
2:15 That's what she said.
Merci d'avoir fourni un, Matlab like, riche outil gratuit..