As he should be. My experience contributing to large open source projects, including as a core developer, has taught me that while people can be pleasant that groups, teams, and committees on most...
As he should be. My experience contributing to large open source projects, including as a core developer, has taught me that while people can be pleasant that groups, teams, and committees on most of these projects are absolutely soul crushingly terrible. Give people with lots of free time a modicum of authority and they lose their minds.
I followed the PEP 572 stuff (and the mountains of other Python related drama) and I cannot understand the level of vitriol. So frustrating.
I skimmed through the official PEP572 documentation, but don't get what all of the drama is about (aside from potentially making code kinda strange to read). For someone why programs in Python but...
I skimmed through the official PEP572 documentation, but don't get what all of the drama is about (aside from potentially making code kinda strange to read).
For someone why programs in Python but has only even made a point of following PEP8 and PEP20, can you give (or alternatively, link to) a brief overview of why this is so controversial?
Here's a good rundown on LWN: https://lwn.net/Articles/757713/ The arguments against it are silly, but not necessarily unfounded. It's like arguing that = and == can be easily confused for one...
The arguments against it are silly, but not necessarily unfounded. It's like arguing that = and == can be easily confused for one another and so we shouldn't have both.
Personally I think it's a good and useful change. Especially with how it simplifies list comprehensions.
Pretty big, but not unexpected, news for the Python world. He's getting old so it's we all knew that at some point he was going to take a step back and start not being an active Benevolent...
Pretty big, but not unexpected, news for the Python world. He's getting old so it's we all knew that at some point he was going to take a step back and start not being an active Benevolent Dictator. I think the really interesting thing is that he cited the PEP572 approval process as one of the reasons for this.
I think that there are good things and bad things about it. I'm not a huge fan, but I don't think it's really the slap in the face that a lot of people seem to think it is. My opinion is really...
I think that there are good things and bad things about it. I'm not a huge fan, but I don't think it's really the slap in the face that a lot of people seem to think it is.
My opinion is really just that a lot of coders like to argue a lot.
Good - he made a terrible decision and stuck his fingers in his ears over the objections of so many experienced developers. It was either quit or lose the 'benevolent' moniker.
Good - he made a terrible decision and stuck his fingers in his ears over the objections of so many experienced developers. It was either quit or lose the 'benevolent' moniker.
The tone of the message makes me feel that he is just fed up with the "techie know it all" types.
As he should be. My experience contributing to large open source projects, including as a core developer, has taught me that while people can be pleasant that groups, teams, and committees on most of these projects are absolutely soul crushingly terrible. Give people with lots of free time a modicum of authority and they lose their minds.
I followed the PEP 572 stuff (and the mountains of other Python related drama) and I cannot understand the level of vitriol. So frustrating.
I skimmed through the official PEP572 documentation, but don't get what all of the drama is about (aside from potentially making code kinda strange to read).
For someone why programs in Python but has only even made a point of following PEP8 and PEP20, can you give (or alternatively, link to) a brief overview of why this is so controversial?
Here's a good rundown on LWN: https://lwn.net/Articles/757713/
The arguments against it are silly, but not necessarily unfounded. It's like arguing that = and == can be easily confused for one another and so we shouldn't have both.
Personally I think it's a good and useful change. Especially with how it simplifies list comprehensions.
Pretty big, but not unexpected, news for the Python world. He's getting old so it's we all knew that at some point he was going to take a step back and start not being an active Benevolent Dictator. I think the really interesting thing is that he cited the PEP572 approval process as one of the reasons for this.
I'm not trying to start a PEP572 argument.
Nor am I, but I have to admit I read a bit of the PEP after seeing this post and it's definitely a pattern I would find useful. ¯\_(ツ)_/¯
I think that there are good things and bad things about it. I'm not a huge fan, but I don't think it's really the slap in the face that a lot of people seem to think it is.
My opinion is really just that a lot of coders like to argue a lot.
HN discussion, by way of subscribing to this post.
https://news.ycombinator.com/item?id=17515492
Good - he made a terrible decision and stuck his fingers in his ears over the objections of so many experienced developers. It was either quit or lose the 'benevolent' moniker.