Linked by Thom Holwerda on Fri 11th May 2007 18:17 UTC, submitted by diegocg
Permalink for comment 239553
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2005-10-09
Last time I checked, you weren't supposed to mod people down just because you disagree with them. You'd be -5 if that were the case. No wonder so many posts get modded negatively even though they are not breaking the rules (off topic/personal insults.) Learn to moderate...
That said, a stable kernel API doesn't hinder development. Just because one person, obviously biased, says so - doesn't make it true. I'd say dtrace was light years ahead of anything linux has to offer. Same with ZFS. Same with zones. The list goes on.
A stable API just means the development model is different. More time planning, less time hacking together code that semi-works. There's a reason why drivers in linux tend to be flaky, especially ones that are newly introduced. Personally, I'll stick with stability. You can have all the bleeding edge functionality that doesn't/barely/halfway works, I'll happily wait for a stable solution that always/fully works instead.
Different models, different methods, both eventually get to the same point. One is a little more rapid at the expense of a lot of stability, one is a lot more stable at the expense of a little bit of rapidity.