I could be mistaken, but I think this kind of happened with ZMQ where one contributor got annoyed and went off to create nanomsg.
Or when people complain about Linus Poettering and Systemd, either how it came to be in certain distributions, or how it took over certain subsystems, or people's behaviour around it - isn't that politics and power structures?
Or that recent post on HN ( https://news.ycombinator.com/item?id=25076197 ) where the Cairo project appears to have nobody left who is able to make a release and the last few years of releases were done by one person working at Samsung, and there hasn't been one since he left, and presumably there was no organizational structure for how to distribute this power to several people, or how to choose and "promote" someone to the job, or if nobody wants to do it, how years worth of effort came to end up on the rocks where nobody even cares anymore, isn't that a broken or absent organization one way or another?
[1] https://mail.python.org/pipermail/python-committers/2018-Jul...
"""In late 2009, the Chair and Red Hat sat down and decided, in a secret meeting, to rewrite the spec. [...] From scratch. By himself. After years and years of committee work. After years of investment by others in working code. Without asking anyone except Red Hat. And then, to force this spec through the working group using his usual tactics: bullying and lobbying. [...]
One of my spin-off projects was the Digital Standards Organization, and I came to understand what was needed to protect a standard from predatory hijack. I summarized the definition of a "Free and Open Standard" as "a published specification that is immune to vendor capture at all stages in its life-cycle." What the "free" part means is, if someone hijacks your working group and starts to push the standard in hostile directions (as Red Hat did), can you fork the standard and continue? Does the license allow forking, yes or no? And secondly, does the license prohibit "dark forks," namely private versions of the standard?
If either answer is "no," then you are at the mercy of others. And when there is money on the table, or even the promise of money, the predators will move in. The AMQP experience gave me a lot of material for my later book on psychopaths. [...]
If we'd managed to build a thriving community around OpenAMQ, it would have survived. So the lesson here is simple: community before code. Today this is obvious to me. Eight years ago, it wasn't."""
And reference this (http://hintjens.com/blog:120) Social Architecture FAQ which talks about rude but highly skilled people contributing to projects (read that with "community before code" and the quote "if you want to go fast go alone, if you want to go far go together" in mind).
His book on Psychopathy was panned on Reddit, as well as on Goodreads:
https://www.reddit.com/r/IAmA/comments/4c27ss/im_pieter_hint...
Likewise, the wikipedia article for Social Architecture has been listed "not notable" for the past four years, and hasn't seen any meaningful edits since 2016.
https://en.wikipedia.org/wiki/Social_architecture
With respect to the author, I'm not surprised. Nerds like ourselves enjoy "discovering" ideas, slapping pretentious labels on them, and then evangelizing them to the whole world... without checking if other people know more about those ideas than we do.
Pieter Hintjens died in 2016.
Is there any actual panning of his book by someone who read his book, in your link? Or anyone who engaged in good faith - e.g. it's a book about his experiences of problem behaviour patterns that hurt others?
The larger point is that the audience he chose to market to, rejected his ideas. Whether or not his audience was acting in "good faith" is irrelevant to his failure to communicate.
Pieter Hintjens (creator of ZeroMQ) wrote a lot about this, and how organizations from big companies to small charities to software projects ought to design their internal structures of roles, titles, voting, auditing, to defend themselves against this kind of attack. Particularly if there's any kind of treasury, an opportunist will become tempted to take that role, but any kind of credit will attract people who want to take the credit without doing the work, power structures will attract people who want the power, and programmers who "just want to code" and avoid politics will find themselves at the bottom of a dysfunctional infected organisation structure with no power, no credit, and being instructed by distorted requests.
IIRC he tried to design the ZeroMQ organisation so that there wasn't any way for one person to insert themselves in a key point.
I'm not sure where on his blog I was reading that, but it's related to his writings about psycopaths[1] as the opportunists, and might be part of his book Social Architecture[2]
[1] http://hintjens.com/blog:_psychopaths
[2] http://hintjens.com/books