Tagged with WinFS
Hey everybody look...its not a Silverlight post ;)
I just finished listening to this interview with Peter Spiro. Peter Spiro discusses leadership in the SQL Server team, Shackleton and WinFS. Its worth a listen as he's one of the smartest guys in MS (in my opinion) and has enough cred to back it up.
In this blog entry by James Kyton, he talks about the next versions of Windows (Fiji and Vienna...in that order). Fuji seems to be Vista 1.1 as it is adding features that were dropped. Of most interest to me is the fact that the WinFS name is rearing is head again. The article states that for Fiji:
"WinFS will be applied over NTFS to give us Virtual Folders (or maybe just Saved Searches)"
While I think its interesting that the new drop of WinFS will be shown at the upcoming TechEd (too bad I couldn't get there this year), what I have seen so far doesn't have me too excited. I played with Beta 1 a bit and was certainly a FanBoy for the early WinFS with Vista before that got yanked.
It looks like WinFS is becoming just another data store (to sit aside SQL Server and Access) with specific hooks for certain types of data. If this is the case and WinFS will not be the next File System (NTFS.next), then I don't know why we should be excited. The "Cairo" promise was a huge promise, but in the decade since, it would seem plausable that someone could make that happen.
I've spent a couple hours digging back into the new WinFS. So far it seems interesting, but only as a new datastore. It doesn't seem to be trying to be the Object File System from teh Cairo days, though that may be because of it's bolted-on status on XP. It is still stored in a SQL Server engine, so that is good. It also looks like the actual files (not just the metadata) are being stored there.
I will probably update my WinFS DB Explorer and release it next week with the new bits. Being able to look at the DB would be fun!
As any of my readers will probably know, WinFS is a hot/sore spot for me. To my surprise, Tom Rizzo dropped a Beta of WinFS (and it supposedly is backwards compatible with XP) on MSDN a day or two ago.
Interestingly is that WinFS will not be included in Vista, but be released post-Vista. It does seem that the 2010 date may be wrong (good!). If I get a chance to dig into it i'll post what I find here.
I really like this post by Adam Barr in response to Scoble's blog about what happened to WinFS. I think Adam is right on with his take on how long-term projects are scheduled. Whether this is what happened to WinFS or not is up to speculation...ok...let me speculate.
WinFS was not a simple project with no or few dependencies. It was dependent on the Yukon team including features that they needed in the core of the storage engine (e.g. Row-level security). At the same time they had to convince the Longhorn UI folks to use WinFS for their desktop changes. Of course, the problem here is pulling from one team, and giving the other team an incomplete tool. WinFS was doomed to failure because of this.
Today, I am quoted in e-Week about my opinion of what's happening to Longhorn...specifically about WinFS. Hope I didn't offend anyone in Redmond ;)
After spending hours digging through Longhorn builds to try and understand WinFS, I have to say that I am really bummed that it is getting pushed out. I think I understand Redmond's approach here, but they've been promising something like WinFS for years now.
As many of you know, I am authoring a new book (with Richard Blewett) on Yukon. When I found out that Yukon did not support row-level security, I feared that WinFS could not be implemented in time. I guess it is time for me to dig into Indigo like I've been meaning to for the last year...
In Luca Bolognese's PDC presentation on ObjectSpaces, he stated in a diagram that you should use ADO.NET's objects DataSets/DataReaders if "You require maximum control/performance/functionality" That seems to indicate that we should not use ObjectSpaces if performance, funcationality and control are a requirement. If this is the case, it would seem that using ObjectSpaces in WinFS is very contrary. WinFS has to be quick...not just fast...lightning fast. We are talking about impatient users.
I think it is important that we get Mike Deem to respond to this in his Blog. I am going to forward this to him and post it up on the newsgroups, but maybe I am missing something.