-
I'd also add Pluto notebooks[1], which when deployed powers interactive sits like MIT's Intro to Computational Thinking[2].
I also get a ton of mileage creating Pluto notebooks and sharing the results for others to run or view a static webpage of the results.
1: https://github.com/fonsp/Pluto.jl
-
InfluxDB
Purpose built for real-time analytics at any scale. InfluxDB Platform is powered by columnar analytics, optimized for cost-efficient storage, and built with open data standards.
-
Source code: https://github.com/zabirauf/blog
P.S: Still dealing with some bugs in deploying PlutoSliderServer so interactivity is broken.
-
Thanks for the reply Jakob. I agree with what you are saying.
When JET.jl works it is great. But for large projects it didn't even return when I tried it. I must have waited at least half an hour once.
VSCode seems like it is offically blessed and maybe I should just cave and use it for Julia. I use vim/neovim for EVERYTHING else though. Taking me out of my extremely custom tmux + terminal + vim workflow just for Julia development annoys me unnecessarily much. Do you know if there's work on getting this to work in vim/neovim?
ErrorTypes.jl, InlineTests.jl, ReTest.jl, SetField.jl all are awesome and I've used them in personal projects. I want to see them in the core language. Maybe ErrorTypes.jl is asking for too much, but tests sorely needs improvement. A SetField like feature literally had a PR open for years and then was just closed
https://github.com/JuliaLang/julia/pull/21912
Without these features in the base language, adoption is going to be so slow. Convincing my team to add a dependency is a lot of work, including updating internal documents, best practices, internal training for how and when to use a certain feature, etc.
