Linked by Julian Djamil Fagir on Thu 14th Feb 2013 22:23 UTC
Permalink for comment 552616
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/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
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
More News »
Sponsored Links



Member since:
2007-03-26
While I agree with you point in theory, your examples are pretty terrible:
- Matt creater DragonFly because he was tired of people putting "band-aids" on FreeBSD, that should fix at one side and break other. This and the desire of have a better "cluster native OS" created this wonderfull piece of software.
Dragonfly is one of the more distinctive variants of BSD. It has a whole boat load of features not seen in FreeBSD.
- PC-BSD = Lack of a stronger desktop initiative by the FreeBSD guys. You know, if they have a installer for "desktop fluffy things" this could be avoided.
Unless things have changed significantly recently, PC-BSD isn't really a fork of FreeBSD, it's more a "distribution". It's point was to give users a no-fuss desktop ready version of FreeBSD. And as PC-BSD is 100% FreeBSD compatible (after all, it /IS/ FreeBSD), I think it deserves it's place as it takes any pressure off the FreeBSD devs from having to cater their limited resources to a multitude of different users expectations (or in layman's terms, FreeBSD can focus on building a solid base and PC-BSD and focus on shipping FreeBSD with the desktop preinstalled and configured to run perfected out-of-the-box).