4 ms·
It is instructive to read GvR's take on Nuitka: https://news.ycombinator.com/item?id=8772124 https://news.ycombinator.com/item?id=8772124 GvR and the old boys
by rlampert 5y ago
It is instructive to read GvR's take on Nuitka:
https://news.ycombinator.com/item?id=8772124 https://news.ycombinator.com/item?id=8772124
GvR and the old boys currently present themselves as CoC proponents, and strategically use the CoC against anyone who criticizes them.
Compare with his current Microsoft sponsored activities. If anyone would use that language against "his" (i.e. Mark Shannon's) project, they'd be out and suffer public defamation in no time.
- wly_cdgr 5y agoWow, didn't realize he could be such a baby Edit: wow GvR's pals and fanboys are salty about someone pointing out what a loser he can be
- gedazz 5y agoWhat does CoC stand for?
- isp 5y agoCoC = "Code of Conduct" I haven't followed Python dev, so can't comment about how the CoC is being used in practice.
- WesolyKubeczek 5y ago> I haven't followed Python dev, so can't comment about how the CoC is being used in practice. In tough situations, CoC powers are inversely proportional to the height of your position on the totem pole.
- Joker_vD 5y agoStill can't believe that this abbreviation is actually in use without any objections while there are talks about needing to rename the Coq language.
- shpongled 5y agoI imagine that most people saying "CoC" out loud are not saying "cock", instead either "Code of conduct", or "cee oh cee".
- WesolyKubeczek 5y agoI also imagine the same people pronounce the other word "cee oh cee kay". I myself pronounce it so it rhymes with and sounds identically to "cock", for several reasons.
- salmo 5y agoI don't love the guy or anything. But you're pulling pieces together from different contexts over almost 10 years to tell your story. The quote was about a presentation in 2013, not the project as it is now. Guido's complaint is mostly that they were equating "compiled" with "performance" and were not rigorous in backing that up. The presenters may have been young. But I'd have made the same complaint. The blog thing was just snarky. That was a period of time when he has admitted he wasn't doing so well as a human being and this is pretty low on the snark-meter compared to other BDFLs. The project page as it is today says very little about performance 'wins' as I read today. In fact, it points out losses, in the same vein as the RedHat issue with Python linked to libpython posted the other day here. Their point doesn't seem to be "make your code go faster", but as an easier mechanism of distribution for some cases. I'm not getting the "his" shot. I haven't seem him take credit for the work, just that headlines do because journalists are lazy. I may have missed something. But the MS team's activities today are things he would have dismissed years ago. He's learned and changed his mind. If he was completely consistent with himself from 2013, I'd think he wasn't that bright. (I'll never understand those kinds of arguments about politicians) You're drawing a line from criticism of a 2013 paper, through his current career, to a malicious intent or conspiracy. That's a lot more defamatory than a valid (but a little rude) critique. You're attacking a person's character, not their work output.
- okdjnfweonfe 5y agocontexts, events, whatever. It doesn't matter. If Kay had listened to any of them, the Python ecosystem would be lacking its best packaging tool, and a significant optimizing tool as well. That is pretty unacceptable. > In fact, it points out losses, Because they have cleared away enough chaff to start encountering these problems with the design of the cpython code itself. There isn't much point in saying X is faster if significant harassers in the python community will make a point of walking out of your talks and later belittling your work online, right?
- WesolyKubeczek 5y ago> He's learned and changed his mind. I don't think so. Call me cynical, but I suspect that Guido went where the money was (one does not simply go out of retirement). Otherwise there would be an apology to the projects he's been consistently berating for years. Good thing Kay Hayen has the perseverance and quite mad planning skills. Today we have a compiler that works better with each release and is capable of delivering results today, while van Rossum's work at Microsoft as of now is largely vaporware I don't have very high hopes for.