3 ms·
deployment + load times: obviously things aren't perfect, Julia is at version 0.4, after all ;) There are a lot of low hanging fruits for compile time and deplo
by simondanisch 10y ago
deployment + load times: obviously things aren't perfect, Julia is at version 0.4, after all ;) There are a lot of low hanging fruits for compile time and deployment, so I'm sure that the situation will look a lot different in a year or two.
I'm not sure why Julia itself should make it difficult to "do the right thing" when exceptions occur...
Real-time 3D rendering is a big area. Will we have virtual reality with ultra low latency in the next year? Definitely not! Can we have 3D CAD/scientific visualizations which hardly stutters? Definitely! Our library is already very smooth and we didn't even start optimizing yet. That's something that seems to be almost impossible in e.g Python (without just calling C for everything).
So while most of these arguments are currently spot on, I do think that there is nothing fundamentally wrong with Julia. And while the maturity is not there yet, you can already be very productive with Julia and build for the future.
- SolarNet 10y ago"I'm not sure why Julia itself should make it difficult to "do the right thing" when exceptions occur..." Untyped, sometimes incorrect, exceptions, https://github.com/JuliaLang/julia/issues/12485 https://github.com/JuliaLang/julia/issues/12485 and related.
- simondanisch 10y agoYeah and there is already an improvement to that: https://github.com/JuliaLang/julia/pull/12541 https://github.com/JuliaLang/julia/pull/12541. Well, anyways, I think you can easily find a lot of unsatisfactory constructs in any language, especially in young ones ;) If they outweigh the advantages is debatable. So far I've been finding satisfactory workarounds for the most daring issues, so for me the conclusion is indeed very positive.