3 ms·
This is oddly something about social proof - the upstream maintainer did not want to break cypress support but needed a high profile public confirmation that th
by lifeisstillgood 3y ago
This is oddly something about social proof - the upstream maintainer did not want to break cypress support but needed a high profile public confirmation that the cypress code was not working (presumably as a final straw that broke the camels back)
This is (bit of a callback) exactly the sort of story I would like the new journalist at lwn.net to deep dive in, give us a nuanced, sympathetic story of what really happened and how such decisions are made.
No blame - just good decisions. it's what we want all over
- phendrenad2 3y agoHmm... but is that what happened, really? It seems like the WPA3 issues have been known about for a long time, and were blogged about by Rachel previously. Seems like the driver maintainer was just being um... we'll go with overly-cautious to remain charitable.
- lifeisstillgood 3y agoAnd really I would like to hear the story, from all sides, charitable (or not ...). Look at it this way, the White House Press Corp is a large number of experienced professional journalists all trying to make sense of a chaotic [#] situation - and while you know US policy matters more than the Linux Kernel, the Linux Kernel underlies trillions of dollars of business in billions of dollars of hardware globally. lwn is the white house press corp for Linux, it does a good job, more can of course be done but as we get more and more reliant on software the choices made by harassed maintainers becomes more important. [#] the chaotic here is not some comment on past or current administrations in the white house - just running a f%#%%g country is going to be chaotic at the best of times.