Linked by David Adams on Thu 1st Jul 2010 08:52 UTC
Permalink for comment 432147
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2006-06-21
This is one of the best ways I've heard it put about why GNU/Linux was such a good match, and why FOSS continues to grow exponentially to this day:
(As a side note, here's an idea for an image evoked by that quote, an image I wish I could draw: a huge and horrible hacked together machine, yet functional, with FOSS written on it and people all over it, hammering and working on it, and a guy filling the tank from a canister labeled "Fun". Linus really nailed it. FOSS has and will always have fun as a core design principle and will be powered by it.)
Back to the topic: In 1997, Eric S. Raymond said: "Release early, release often. And listen to your customers." Linus did that (instinctively, years before ESR said it.). The result is above. The FSF did not.
They had a chance, with BSD 4.4-Lite, but didn't take it (granted, Mach seemed like the best choice at the time; it is only in hindsight that the choice appears wrong). Then again, they tried so many microkernels across the years and none of them worked as well as they'd have hoped. That says something about the microkernel vs monolithic debate; microkernels may be, in theory, more advanced in some aspects, but in real life their developments poses problems which cannot be handled by the HURD team's limited resources.
And so it has come to pass that HURD is nowadays a classical example of a software project that always chases moving targets. "Perfect design"? There's no such thing.
Research is fine and all, but at some point you have to come out of the lab with something that (1) works and (2) is needed. HURD doesn't fulfill either of these requirements.
Edited 2010-07-01 14:04 UTC