Linked by Thom Holwerda on Mon 7th Jun 2010 10:15 UTC, submitted by kragil
Thread beginning with comment 428806
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2008-10-23
"Enterprise" refers to software developed on a schedule with managers dictating the necessary set of features, and then engineers adapting to that. Functionality that there is no time to redesign will remain forever as kludges.
btrfs will succeed exactly because it isn't "enterprise". The software is evolved naturally, with no deadlines and no managers to dictate a set of features. Functionality that is consistent and sound from an engineering perspective gets implemented. Functionality that isn't, will be sent back to the drawing board until it is, or never implemented at all.
And yes, many btrfs developers have a long experience working with file systems.
tl;dr: btrfs is ZFS done right. btrfs is to ZFS as Linux is to Solaris.
My god, your post is so funny (and wrong in every sentence) I can't even think of what to respond. You know about Solaris because you read about it once in a Linux magazine, right?