Hey folks! There was a pretty good critical article written about Julia recently called “Why I no longer recommend Julia” by Yuri Vishnevsky There is an ongoing discussion about the article that has largely been constructive on Slack. Hoping to capture some of these thoughts here to provide actio…

[image] JosePereiraUA: part of the problem stems from the lack of incentive for developers (which are mostly from the academic world) to properly document, add tests and continuously maintain packages and fix bugs. More often than not, once a package works as intended for that particular researc…

It’s ironic that this post has been up for a month and a half now, and has received immense attention across various forums (including 250+ comments in this thread), but Yuri is still pointing out indexing bugs such as `first` sometimes returns incorrect results when used with nonstandard indexing ·…

Note that (at least for the first one), the @inbounds call is safe. The problem is a just an integer overflow.

[image] jishnub: Yet, people are busy debating on broader ideas instead of acting on issues that the original post had raised. But, both of those were acted on. Haven’t all the raised issues been acted on, as far as possible? I mean, except for some of the broader issues…

Guessing you did that simple grep for @inbounds yourself already then, and you’re filing issues as I type? :stuck_out_tongue:

[image] Timothy: I have a serious discoverability problem with Julia. Or perhaps Julia has the problem. The manual explaining Julia concepts is pretty good, but the documentation for most packages I need to use is inadequate. There’s a lot of friction even when doing simple things. For example, …

[image] DNF: But, both of those were acted on. Haven’t all the raised issues been acted on, as far as possible? I mean, except for some of the broader issues… Yes, the response of the community to resolving filed issues has been fantastic, but my point was more about finding the issues in the…

Haha that’s awesome, thanks for putting in the time. Unfortunately it does end up being whoever feels the strongest about problems that has to fix them a lot of the time. I do think people are responding to the post seriously, but open source is slow and we’re all busy. For example I’ve got the st…

Very well written article! I do have one point of criticism – the description of object-oriented programming. It is such a common mistake to make, given that not very many people are familiar with older OOP implementations. Common Lisp as an example, does not couple methods to classes. It behaves in…

[image] mfiano: I do have one point of criticism – the description of object-oriented programming. It is such a common mistake to make, given that not very many people are familiar with older OOP implementations. That’s why I sticked to the Java, C#, C++ definition of OOP. Most people think o…

Discussion on "Why I no longer recommend Julia" by Yuri Vishnevsky

Community

mbauman Split this topic July 1, 2022, 1:55am 289

13 posts were split to a new topic: Workflow challenges with redefining structs (from “Why I still recommend Julia”)

Topic		Replies	Views
At present, in what aspects is Julia still relatively weak compared to other mainstream programming languages? New to Julia question	66	9483	February 5, 2024
Did Julia community do something to improve its correctness? General Usage	219	14243	November 4, 2023
Fixing Package Fragmentation Community	71	6285	May 28, 2023
Correctness and Multiple Dispatch (Help explain to a julia noob) Community question	13	1157	April 30, 2025
How can we create a leaner ecosystem for Julia? Statistics package , proposal , time-series , machine-learning	101	10825	October 15, 2020

Discussion on "Why I no longer recommend Julia" by Yuri Vishnevsky

Related topics