News for hackers. Stuff that matters.
Re:Nimony: A New Compiler for Nim by torginus on Tuesday November 17, 2026 @07:26AM (#50530476)
Is this a Python 2/3 situation?
Re:Nimony: A New Compiler for Nim by christophilus on Tuesday November 17, 2026 @07:58AM (#50530768)
Might be, but Nim is statically typed, and we have LLMs now, so migration should be pretty trivial, is my guess.
Re:Nimony: A New Compiler for Nim by pjmlp on Tuesday November 17, 2026 @08:34AM (#50531144)
Speaking from the stand of Java and .NET breaking changes, it is not, some folks will cling to the old world no matter what.
Re:Nimony: A New Compiler for Nim by simlevesque on Tuesday November 17, 2026 @08:57AM (#50531433)
Nim 2 isn't as popular or ingrained as Java 8 or .NET Framework.
Re:Nimony: A New Compiler for Nim by pjmlp on Tuesday November 17, 2026 @09:09AM (#50531598)
True, that doesn't mean that folks will feel like migrating, unless they see a value in doing so.
Re:Nimony: A New Compiler for Nim by torginus on Tuesday November 17, 2026 @09:04AM (#50531537)
I'm not a Python guy, but my understanding was that the reason why Python 2 stuck around for so long was that some people preferred it over 3
Re:Nimony: A New Compiler for Nim by stakhanov on Tuesday November 17, 2026 @09:39AM (#50532014)
I think it's all about corpus weight.

When Python did the migration, it had a good flow of new investments coming into it and delivered good reasons for why those should go to Python 3 rather than 2. At the same time, it also already had a base of existing investments in Python 2 delivering better ROI without the added cost of a migration, and the sum of that exceeded the critical mass it took to make it economical to keep both versions of the ecosystem around.

With Perl you are seeing what it looks like when you have zero new investments coming in and no good reasons for why new investments should go to Raku. (Because: Just use Python). You do still have a non-negligible base of existing investments in Perl 5 and those deliver better ROI without the added cost of a migration. So my prediction is that Perl 5 will stick around, and Raku is dead on arrival.

With Nim it might be the other way around: Good reasons for why new investments should go to Nim 3 rather than Nim 2, and not all that much existing investment in Nim 2. If Nim 3 sees healthy adoption, it might well be more economical to re-deploy ecosystem maintenance to Nim 3 and migrate most of the existing code, ratheer than keep two versions of the ecosystem going.

Re:Nimony: A New Compiler for Nim by ghshephard on Tuesday November 17, 2026 @12:51PM (#50535314)
I know you realize this, but it is worth emphasizing that Perl 5 vs Perl 6 is a not comparable to Python 2 to Python 3. For 98%+ of code, Python 2 and Python 3 are mostly identical, and the conversion, even in massive code-bases, is completely mechanical for 99.5% of the code.

Perl 5 and Perl 6 (Raku) are different languages.

Re:Nimony: A New Compiler for Nim by nagaiaida on Tuesday November 17, 2026 @04:37PM (#50538539)
it's also worth emphasizing basically all the changes raku made filed off an extremely sharp edge of perl
Re:Nimony: A New Compiler for Nim by Beretta_Vexee on Tuesday November 17, 2026 @10:07AM (#50532389)
It was largely a question of the existing codebase. It took years to convert all the obscure scientific libraries from Python 2 to Python 3.

The migration was no easy task. So all the projects already written in Python 2 remained on version 2. Until the day they reached a dead end and were forced to migrate.

Re:Nimony: A New Compiler for Nim by ghshephard on Tuesday November 17, 2026 @12:48PM (#50535255)
It was inertia. I was working at a company in 2017 in which 100% of the very extensive code base was written in Python2. The Python3 migration was done in a weekend and was mostly a nothing burger, as, with few exceptions, the conversion was 100% mechanical and just worked. The print vs print() was the most visible change, and the str/bytes change was a genuine improvement.

Except for no longer being confused about whether I was reading bytes or "strings" (Python3 eliminated that confusion), and having to remember for roughly a year to use "()" when using print, I don't believe I even really noticed that big a difference between the two.

Honestly - I'm surprised that python managed to hold on long enough for "uv" to be released and solve all the packaging/venv pain - that was a real problem with python for 15+ years and wasn't solved until 2024.

Re:Nimony: A New Compiler for Nim by jibalt on Tuesday November 17, 2026 @10:54PM (#50541673)
No. a) Python had vastly more users. b) That change hit things that were much more "mainstream" in the language, like string encoding and print as a function vs. a statement.