4 ms·

I don't use Python nearly as much as I used to (mostly Go now) but changes like this make me realize how much I appreciate the Go 1 compatibility guarantee. I h

I don't use Python nearly as much as I used to (mostly Go now) but changes like this make me realize how much I appreciate the Go 1 compatibility guarantee. I have Go libraries from 1.6 that I have upgraded without a second thought. These sort of PEPs (remember the walrus operator?) seem like fundamental language changes that serve to divide the community without much gained. Although I will say, Go has made it much easier to be involved in the language design process.

qbasic_forever 5y ago
Nothing is immune, these are fundamentally people and person problems which can and will affect any language. It's ironic that just this week one of the core maintainers of Perl stepped down because of backlash and harassment from other maintainers over proposed changes (https://news.ycombinator.com/item?id=26779152 https://news.ycombinator.com/item?id=26779152). Python is a little younger than Perl but also faced similar problems--Guido had so much backlash against proposals that he stepped down too (https://news.ycombinator.com/item?id=17515492 https://news.ycombinator.com/item?id=17515492). Go is younger than either of those but not immune to the same fate--just look at the total divide and amount of controversy created over things like generics or modules in the community. There's no magic fix for this--if an organization is going to thrive and grow (or even just survive) for 30+ years it has to address those issues sooner rather than later. Burnout, at all levels, is real.