3 ms·
You mean the way rakudo took over the entire perl ecosystem when it finally arrived? I suspect a lot of the controversial decusions made doing the 2to3 migrati
by Stranger43 4y ago
You mean the way rakudo took over the entire perl ecosystem when it finally arrived?
I suspect a lot of the controversial decusions made doing the 2to3 migration by the python foundation was deliberately designed to avoid a situation similar to what happened to perl when the time came to cleanup some of the old cruft from the language.
- xdennis 4y agoThe difference is that Perl 6/Raku was a huge change from Perl 5. For Python, the small improvements weren't worth the break in compatibility.
- Conan_Kudo 4y agoYou underestimate how big of a change Python 3 actually was. Changing how strings and bytes are handled has a huge blast radius. It broke almost every library or application I worked on. Everything else was peanuts to that semantic change. It was a necessary change too. Supporting Unicode strings or mixed-encoded strings was absolutely awful in Python 2 and almost not worth doing. Python 3 made that work properly. Arguably, the only real mistake was using UTF-16 instead of UTF-8 for strings. But back then, nobody knew what would take off and Windows natively uses UTF-16, so...
- sigzero 4y agoPython 2 to 3 wasn't even close to the change of Perl 5 to 6 (later Raku). Sorry, it just isn't even a comparison.
- mort96 4y agoPython 3 had a HUGE impact on existing code, yes. Everything broke. But Python 3 didn't actually change much for the people writing new Python code, it just broke the old code. Raku is a completely different language from Perl. Writing Raku instead of Perl 5 is like writing Rust instead of C++.