<story><title>Julia 1.6 addresses latency issues</title><url>https://lwn.net/SubscriberLink/856819/c865652ad4dc06d0/</url></story><parent_chain></parent_chain><comment><author>smabie</author><text>So I used to be a big proponent of Julia, and in some ways, I still am. But I very recently tried to write a high performance production system in it, and was sorely disappointed. The tooling is just so buggy and it&amp;#x27;s clear that the community isn&amp;#x27;t really interested in using it for anything besides modeling&amp;#x2F;research in a Jupyter notebook.&lt;p&gt;Things that kind of suck about using Julia for production:&lt;p&gt;1. Never could get Revise to work, had to restart my REPL everytime I changed any code. Even though Julia 1.6 was a lot faster than 1.5, it still took too long.&lt;p&gt;2. Couldn&amp;#x27;t find a static type checker that actually worked (I tried JET and StaticLint). I feel like static typing is just so important for a production system, but of course the community isn&amp;#x27;t really interested because of the research focus.&lt;p&gt;3. Editor tooling. The LSP server absolutely sucks. I first tried using it with emacs (both lsp-mode and eglot mode), but it would crash constantly. I think switched to VSCode (much to my chagrin), and that worked marginally better though still very poorly. It was clear that the LSP server had no idea what was going on in my macro heavy code. It couldn&amp;#x27;t jump to definitions or usages much of the time. It could never correctly determine whether a variable was unused or misspelled either. Coupled with the lack of static type checking, this was &lt;i&gt;extremely&lt;/i&gt; frustrating.&lt;p&gt;4. Never felt like the community could answer any of my questions. If you have some research or stats question, they were great, but anything else, forget about it.&lt;p&gt;Will all of that being said, I do still use Julia for research and I find it works really well. The language is very nicely designed.&lt;p&gt;All and all, I decided to ditch Julia and decided to go with Rust (after some consideration of OCaml, but unfortunately the multi-core story still isn&amp;#x27;t there yet) and am a &lt;i&gt;lot&lt;/i&gt; happier.</text></comment>
<story><title>Julia 1.6 addresses latency issues</title><url>https://lwn.net/SubscriberLink/856819/c865652ad4dc06d0/</url></story><parent_chain></parent_chain><comment><author>Buttons840</author><text>I&amp;#x27;m a big fan of Julia. It does live up to its speed claims. I&amp;#x27;ve implemented the board game Go in Python, Rust, and Julia and Julia is definitely closer to Rust in speed. Same algorithms were used for all implementations.&lt;p&gt;Julia&amp;#x27;s time to first plot still has some problems. The Plots library can build animations, but the time to first animation on my computer is like 10 minutes, and the time to second animation is another 10 minutes. Probably just a bug, I haven&amp;#x27;t found any other case that takes so long.&lt;p&gt;I&amp;#x27;ve also mentioned before that a reinforcement learning algorithm I ported from Python&amp;#x2F;PyTorch to Flux was faster, not because of training times, but because of all the other stuff (and RL has more &amp;quot;other stuff&amp;quot; than supervised learning) that goes on outside the core training loop is so much faster.</text></comment>