WinFS appears to be the main casualty, having already been curtailed. A year ago Microsoft confirmed that Longhorn wouldn't, as expected, introduce an entirely new database storage architecture in which file systems NTFS would be a plug-in. Rather, Microsoft would add database like properties to NTFS. Business Week reports that the new features of WinFS will only work on local storage rather than across networks. That's been pushed into Blackcomb, which is way out towards the end of the decade.Allow me to toot my horn for seeing this one coming over a few items I posted in recent months.
To reiterate I think the problems being addressed by WinFS are far better addressed not as a file system but by rethinking "the database". But then that would even more directly eat into the SQL Server cash cow. Either way, there are some tangly knots along the way that had simply been bypassed in the several WinFS presentations I've seen.
This is a good call, but too bad Microsoft has put countless hours into the WinFS over a decade now, if you count the origins back in Cairo-pre-Win95. If I read the above as WinFS will always be a "local file system" capability, then this is a total loss. Come back when this thing understands multiple users and runs on the network with location independence.
i.e. Come back when it is *really* a database, but not complex and not naive and self-managing... this is not easy.
Reports from Redmond suggest that the Avalon UI archtecture and the "managed code" API are also likely to be trimmed in order to get this most reluctant of steers out of the gate.Two for two? Can we say goodbye to the waste-of-time XAML yet?