Jeff Bezanson - What's the deal with Julia binary sizes? 

I always enjoy Jeff Bezanson's talks.

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.

Great talk! Can you please detail how to remove LLVM from the geneerated lib ?

2:15 That's what she said.

21:50 😂

If nothing useful is exported from the toy example, shouldn't the compiler just be able to make it all a noop?

Merci d'avoir fourni un, Matlab like, riche outil gratuit..

so you went from "omg, that's bananas!" to "oh nelly, that's bloated!"