Re:Sunsetting Python 2
by koreth1 on Monday September 09, 2019 @09:44AM
(#20918063)
I would have said Java, but then they decided to shove modules down everyone's throat.
[ Parent
| on HN ]
Wouldn't Java 1.0 code still work in Java $LATEST even with modules? As i understand it the question was about keeping stuff working, not refusing to add new stuff.
1.1 is what would still work. There was not much Java 1 code in existence.
Java 1.4 to 5 was annoying and the last release to introduce a lot of source code in compatibility. Which was sometime in 2004. Modules is mostly figuring out what switches to set on startup, not so much refuses to work.
Re:Sunsetting Python 2
by chrshawkes on Monday September 09, 2019 @11:48AM
(#20919234)
I would say the Perl but then the Perl 6 fiasco made Python 3 look like a model citizen for upgrading code.
Re:Sunsetting Python 2
by mirchibajji on Monday September 09, 2019 @03:00PM
(#20921180)
Perl5 is not being EOL'ed in favour of Perl6. When the time does come around for Perl5, I would guess that only a small fraction would migrate to Perl6.