4 ms·
I would have said Java, but then they decided to shove modules down everyone's throat.
by koreth1 7y ago
I would have said Java, but then they decided to shove modules down everyone's throat.
- Crinus 7y agoWouldn'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.
- jerven 7y ago1.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.
- chrshawkes 7y agoI would say the Perl but then the Perl 6 fiasco made Python 3 look like a model citizen for upgrading code.
- mirchibajji 7y agoPerl5 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.