News for hackers. Stuff that matters.
Re:A response about dep and vgo by munificent on Friday July 27, 2018 @05:20PM (#17629505)
> If that decision really turns out to be so bad then it will be forked and a wiser leader(s) will have their shot at decision making.

No, that doesn't work in practice. The network effects are so insanely dominant in open source projects that forks are nowhere near an efficient market.

Re:A response about dep and vgo by stcredzero on Friday July 27, 2018 @05:26PM (#17629554)
The network effects are so insanely dominant in open source projects that forks are nowhere near an efficient market.

The market doesn't have to be anywhere near efficient. It just has to allow any escape whatsoever from a death-march/death spiral.

Re:A response about dep and vgo by nicpottier on Friday July 27, 2018 @05:49PM (#17629707)
Open Source is absolutely chock full of examples of this.
Re:A response about dep and vgo by munificent on Friday July 27, 2018 @07:57PM (#17630514)
That's survivorshop bias. Yes, occasionally a fork takes over. It very rarely succeeds and usually only in cases where the original is so toxic that it cancels out its own network effects. node.js is a good example of that. And then even there note how they eventually unforked.
Re:A response about dep and vgo by jessaustin on Friday July 27, 2018 @10:25PM (#17631150)
It is really uncharitable to describe the node fork as "so toxic". People disagreed, but there's nothing wrong with that. I felt like the subsequent "merge" happened fairly quickly and with minimal drama.

Also this seems like a misuse of the term "survivorship bias". You claimed upthread that forks don't work because of network effects. The response was "some forks work". That is a direct refutation, no matter what the percentages are. Besides, you're misunderstanding the varied purposes of forks. I have several forks right now, not because I hate the original maintainers but because it was convenient to change a small thing for my own purposes. Whether or not upstream eventually agrees with me, my fork "works" perfectly well.

Re:A response about dep and vgo by ansible on Friday July 27, 2018 @06:51PM (#17630111)
And sometimes the new community wins out over the existing one. LibreOffice vs. OpenOffice, X.org vs. XFree86, etc.
Re:A response about dep and vgo by geodel on Friday July 27, 2018 @07:09PM (#17630224)
Libreoffice vs Openoffice, Hudson vs Jenkins, and there would be so many more.
Re:A response about dep and vgo by weberc2 on Saturday July 28, 2018 @09:27AM (#17633049)
Like the OP mentions in another comment, this is survivorship bias.
Re:A response about dep and vgo by Vendan on Friday July 27, 2018 @05:29PM (#17629574)
It has literally happened before. Look into the node.js/io.js fork.