4 ms·
Let's think of Python 3 as Perl 6 that got done on schedule. There may be many good reasons to use Python 3 today, but it is not like Python 2.x is not good eno
by FraaJad 17y ago
Let's think of Python 3 as Perl 6 that got done on schedule. There may be many good reasons to use Python 3 today, but it is not like Python 2.x is not good enough as-is or it is standing still.
With Guido's recent focus on not adding new semantics to the language, it's clear that he wants people to focus on getting stuff working on 3.x without changing more stuff in the core.
Optimizations to the language via unladden swallow, rewriting standard libararies etc., are a right step in that direction.
- chromatic 17y ago> Let's think of Python 3 as Perl 6 that got done on schedule. That seems silly to me. Guido announced that he'd start working on Python 3000 part time in early spring 2000; that's eight and a half years. Now compare the goals of Python 3 to the goals of Perl 6. Python 3 didn't really change much over Python 2, in comparison. Sure, Python 3 came out a little bit sooner than Perl 6, but it was also a lot less work to produce.