2 ms·
both forks typically end up poorer because of members lost. I strongly disagree. Off the top of my head: XFree86/Xorg, Mozilla/Firefox, Debian/Ubuntu, Rails/Me
by erikpukinskis 16y ago
both forks typically end up poorer because of members lost.
I strongly disagree. Off the top of my head: XFree86/Xorg, Mozilla/Firefox, Debian/Ubuntu, Rails/Merb... these were all cases where the existing community had calcified in some key area and a fork was necessary to create a space where important work could get done.
And in most of those cases, not only was the fork stronger than the trunk in (some) specific areas, the fork actually led to the trunk getting stronger. Not only were patches merged, but entire projects, community values, development practices, etc were.
XFree86 is an exception, but organizational paralysis was what necessitated the fork, so it's not surprising they were also unable to respond to the fork.
But I just don't buy your notion that forking is somehow unhealthy and destructive. It's one of the most valuable ways we have to keep open source code, ideas, organizations and practices fresh, healthy, and vibrant.
- malandrew 16y agoI agree that there are exceptions. In the case of HN, I don't see how forking would be of benefit, especially since HN is so strongly linked to YCombinator, the startup incubator/school that tends to attract the most talented up-and-coming startups.