Linked by Thom Holwerda on Sun 25th Jun 2006 21:16 UTC, submitted by Dolphin
"WinFS has been officially pulled out of Microsoft's road map for products and services - permanently. People all around the web are shocked and complaining. But the thing is: who didn't expect this? Although no one came out and said it directly, no one spoke of WinFS except as a distant memory, it was quite obvious that people didn't buy Microsoft's story of it shipping separately. If people believed, the shock and outrage today would be ten times as big as it was when the LH project was rebooted and WinFS torn out with the strings still hanging. But the question many people are asking these long years later is: what is WinFS anyway? And what's the big deal if everyone already knew it wasn't coming?"
Permalink for comment 137313
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-05-15
Weakness on NTFS:
1. Windows NTFS do not do well against FS fragmentation. (UNIX employ writting stragety to eliminate fragment and ever Mac OS X has builtin code to defrag in backgroud). I wait MS since MS-DOS's era to do what UNIX already did. Waste users $ buy defragmenter software.
2. 4K default cluster size for NTFS quite awesome. We can define to use bigger than 4K cluster size for NTFS to lower no. of fragmentation and improve I/O performance, but 3rd party defragmenters do not allow to defrag bigger than 4K cluster size (I test it under Diskeeper 9 and O&O Defrag 7).
In my opinions, elimination of FS fragmentation and > 4K cluster size at NTFS default (i.e. FreeBSD has chagne from 8K to 16K cluster size) are more benefit for user than Database FS (WinFS).