Correctness and composability bugs in the Julia ecosystem (2022)
1–10 of 83 posts
Re: Correctness and composability bugs in the Julia ecosystem (2022)
#2@dang: I'm not sure exactly when this was posted since it seems to have no date, but it's at least (2022) per HN's link from that year: https://news.ycombinator.com/item?id=31396861
I mention this because this is definitely the sort of content that can age poorly. I have no direct experience, I've never so much as touched Julia.
Re: Correctness and composability bugs in the Julia ecosystem (2022)
#3I think I may have missed what alternative is being recommended instead, after scrolling through the whole article.
Re: Correctness and composability bugs in the Julia ecosystem (2022)
#4@dang: I'm not sure exactly when this was posted since it seems to have no date, but it's at least (2022) per HN's link from that year: https://news.ycombinator.com/item?id=31396861 I mention this because this is definitely the sort of content that can age poorly. I have no direct experience, I've never so much as touched Julia.
It cites an example from 2024 so the text has definitely been updated since 2022.
Re: Correctness and composability bugs in the Julia ecosystem (2022)
#5I think I may have missed what alternative is being recommended instead, after scrolling through the whole article.
None
Re: Correctness and composability bugs in the Julia ecosystem (2022)
#6> My conclusion after using Julia for many years is that there are too many correctness and composability bugs throughout the ecosystem to justify using it in just about any context where correctness matters.
Does this have any impact on the cosmological emulator written in Julia?
Re: Correctness and composability bugs in the Julia ecosystem (2022)
#7I think I may have missed what alternative is being recommended instead, after scrolling through the whole article.
Hinted as Python not having these issues.
Re: Correctness and composability bugs in the Julia ecosystem (2022)
#8I think I may have missed what alternative is being recommended instead, after scrolling through the whole article.
The OP shows examples of people being unable to solve a problem in Julia that they solve quickly after switching to PyTorch, Jax, or TensorFlow, so the OP is implicitly recommending those alternatives.
Re: Correctness and composability bugs in the Julia ecosystem (2022)
#9I think I may have missed what alternative is being recommended instead, after scrolling through the whole article.
He doesn't recommend any alternatives. Looking at his GitHub profile (https://github.com/yurivish?tab=repositories), looks like he's using a lot of Rust and Go these days, though looks like mainly for projects unrelated to the sorts of data crunching suitable for Julia, R, etc
Re: Correctness and composability bugs in the Julia ecosystem (2022)
#10I like the design of the language, but I eventually went through too many cycles of "fast compilation and/or module caching is coming in the next release" and "ahead of time compilation is coming soon" and got burned out. I remember believing the same stuff from java for years until forgetting about it.