Hi everyone, I made a video about reducing Julia’s latency after a conversation with a friend who said that they really wish all of this information was in one place. Hence, you get this video. Possibly part one of two, where in the second I cover the packages I referenced in the outro of this one (JuliaFormatter, JET, Aqua, and Cthulhu). [Minimise Julia's Latency: Revise, PrecompileTools, and PackageCompiler] Feedback is very welcome! I will mention, though, that while I do talk about some advanced topics, I try to not go into too much detail so if I glossed over some parts of the video or didn’t mention stuff (how PackageCompiler can do so much more or that the part that I discussed will hopefully one day be redundant) it might be because I decided not to put it in. Thanks for watching and filling out my workflow survey if you did :wink:

This has No Boilerplate vibes, and I love it!

Very cool tutorial, taught me a few things, and I loved the drawings :heart_eyes: A minor caveat was that the code was changing way too fast (and maybe in too small a font) for me to follow. Perhaps something to keep in mind for the next video? I also agree that these tips and tricks should stop being part of an unspoken lore and start being explicitly documented in one place. I would love to draft a blog post for the Julia blog, something like “Modern Julian workflows”, where I give an annotated list of what it takes to easily use, and then develop, packages. If you and my idol @jakobnissen would like to contribute, we could get this going.

[image] mrufsvold: This has No Boilerplate vibes, and I love it! He was one of the two channels whose style I wanted to emulate along with code_report. Tris got me into Rust, Conor got me into array languages, I hope I can get someone into Julia :slight_smile: [image] gdalle: I loved the drawings <3, I wish the whole video were done with them [image] gdalle: an annotated list of what it takes to easily use, and then develop, packages Very useful! I’d love to get involved.

[image] jacobusmmsmit: Very useful! I’d love to get involved. I’ll open an issue someday soon to discuss the structure, and tag you in it

This video tutorial should be placed somewhere in the official docs! :clap:

[image] [Seeking feedback] Blog post about "Modern Julia workflows"? Tooling Hi everyone, After watching a nice video by @jacobusmmsmit yesterday, I sat down and thought about all the lore that experienced Julia users keep in their heads. How to write and share code properly, which packages to use and when, etc. This accumulated knowledge makes our development experience very pleasant, but it is long to acquire and beginners don’t always know where to look. The official documentation is only part of the story: best practices involve a flurry of external packages, whic…

Useful content, great presentation ,chad voice. 10/10.

Great video! Really looking forward to the second one you mentioned :slight_smile:

I love your voice. To the topic: Why do we adopt these techniques optionally, instead of making them the default workflow of everyone? I play around with Julia in VSCode, and every time I hit the ‘run in the REPL’ button in the right top corner, it takes ages to start up. The system feels incredible unresponsive, and that already with a few lines :frowning: Is this the experience we like to give to new users?

Creating new packages, and utilizing Revise.jl the way you showed us, is pretty much contradicting the purpose of a REPL to me. A REPL is meant to give me straight access to a development environment, and not something that needs complicated setup, that the vast majority of newbies will not even consider to use. I certainly wouldn’t, and you outline one of the core issues with our REPL workflow. But the proposed solution is even worse to me, than just having to wait half an eternity for the REPL to come up, and then me having to think to close it, if there are still old functions stored. It complicates things just further, in my opinion. And we do have an interpreter, that I would like to use as the default backend for the REPL. No huge startup, and more suitable for small code. I just think adding @interpret for every execution can be skipped, and loading it in manually seems also counterintuitive to new users. Is there a huge benefit to JIT all the code at the standard REPL instead?

[Video] How to Reduce Julia's Latency

Community

gdalle June 14, 2023, 6:09am 7

Topic		Replies	Views
Video tutorial: Julia REPL tips and tricks New to Julia tutorials	5	1369	October 25, 2019
Is there a good way to run an interpreted IJulia session? General Usage	4	483	August 10, 2022
How to effectively develop in Julia? New to Julia	17	1966	May 23, 2021
Ways to make slow/sluggish REPL/interactive development experience faster? Performance repl , ttfp	35	6162	July 23, 2019
Will Julia ever fix its "using ..." latency problems? Performance	68	8468	April 25, 2022

[Video] How to Reduce Julia's Latency

Related topics