←back to thread

2024 points randlet | 4 comments | | HN request time: 0.552s | source
Show context
bla2 ◴[] No.17515883[source]
> I don't ever want to have to fight so hard for a PEP and find that so many people despise my decisions.

Leading a large open source project must be terrible in this age of constant outrage :-(

replies(9): >>17515955 #>>17515972 #>>17516193 #>>17516427 #>>17516776 #>>17516884 #>>17517282 #>>17517716 #>>17517821 #
symmitchry ◴[] No.17515972[source]
I'm a little confused though, by his feelings here. Why did he feel the need to "fight so hard for a PEP" if it was so controversial, and everyone was outraged?

I do understand people's points about "the age of outrage" and "internet 2018" but still: the PEP wasn't generally accepted as being a fantastic improvement, so why did he feel the need to fight so hard for it?

replies(5): >>17516128 #>>17516129 #>>17516223 #>>17516774 #>>17519017 #
jnwatson ◴[] No.17516128[source]
It was controversial syntax, inline assignment-as-expression. There's always a tension between "keep it simple stupid" and "let's make it better", especially when a large user demographic of Python are non-professional-programmers.

Interestingly, C++ is going through the same process, with lots of great ideas being proposed, but the sum total of them being an even more complicated language (on top of what is probably the most complicated language already).

Python has been successful, IMHO, because Guido has made several brave, controversial calls. Python 3 breakage and async turned out to be prescient, fantastic decisions.

replies(6): >>17516204 #>>17516226 #>>17516681 #>>17517178 #>>17517212 #>>17533584 #
Redoubts ◴[] No.17516681[source]
> Python has been successful, IMHO, because Guido has made several brave, controversial calls. Python 3 breakage and async turned out to be prescient, fantastic decisions.

A lot of companies are choosing new languages over porting python from 2 to 3.

replies(1): >>17516973 #
Daishiman ◴[] No.17516973[source]
Name one.
replies(2): >>17517477 #>>17517863 #
1. liveoneggs ◴[] No.17517863[source]
Google replacing python with Go?
replies(3): >>17518043 #>>17518414 #>>17533714 #
2. Daishiman ◴[] No.17518043[source]
That has little to do with Python 3 and a lot to do with the scale of Google's services where high performance is really important and where refactoring in static languages is easier.
3. joshuamorton ◴[] No.17518414[source]
This also isn't really true. Google is certainly replacing certain things with Go. But its not replacing python with go.
4. webmaven ◴[] No.17533714[source]
I understand that had more to do with their "Unladen Swallow"[0] work being rejected than anything related to the transition to Python3.

Since Google couldn't convince folks to let them make Python faster, they created a NEW language instead.

[0] https://www.python.org/dev/peps/pep-3146/