3 ms·
> I really feel its time for Python 3 to freeze language features. This PEP and the previous walrus operator fiasco feel like people trying to morph Python into
by heavyset_go 6y ago
> I really feel its time for Python 3 to freeze language features. This PEP and the previous walrus operator fiasco feel like people trying to morph Python into something that it isn't with one kludge after another. This will not lead to a robust language, but instead another Perl 5 monstrosity of complexity.
I disagree entirely. This is how Python will be left behind. It needs to be able to compete with languages that adopt new features and paradigms.
For example, new Ruby releases got optional typing and pattern matching. Even Java is getting pattern matching[1]. This is where the developer zeitgeist is heading, and if Python doesn't keep up, it'll be replaced with a language that does.
[1] https://benjiweber.co.uk/blog/2021/03/14/java-16-pattern-matching-fun/ https://benjiweber.co.uk/blog/2021/03/14/java-16-pattern-mat...
- makapuf 6y agoThis is where python3 can be left to rest and be maintained while python4 is trailing forward by being compatible?
- easton 6y agoThat won’t happen though. When the 2->3 split happened, people swore up and down “I won’t stand for this! You can’t break Python! We’ll fork it and nobody will ever have to do these changes.” Now, everyone is on Python 3 for new stuff, and companies are trying to transition to 3 or paying for the company (who’s name escapes me) that does security updates to 2.7. It never works out. It’s best for the PSF to try to reduce breaking changes and try to keep everyone together.
- makapuf 6y ago2 to 3 was about incompatible changes, and many companies switched to 3 because of eol of python 2.7, or its EOL would have been a minor event. What I thought about was a backwards compatible branch. We would then see if people need more features or if its enough, but I understand I'm only suggesting more(maintenance) work.