Quentin Clark has posted a new entry entitled Update to the Update on the WinFS team blog that answers some of the questions that have been raised since his post on Friday about the status of WinFS. He writes
Is WinFS dead?
Yes
and No. Yes, we are not going to ship WinFS as a separate, monolithic
software component. But the answer is also No - the vision remains
alive and we are moving the technology forward. A lot of the technology
really was database stuff – and we’re putting that into SQL and ADO.
But some of the technology, especially the end user value points, are
not ready, and we’re going to continue to work on that in incubation.
Some or all of these technologies may be used by other Microsoft
products going forward.
Does your plan for WinFS have any impact on Windows Vista?
There is no impact on Windows Vista. We announced back in August 2004 that WinFS would not be in Windows Vista.
Will the "Relational Filesystem" ever be in Windows?
Hey
– we are very busy finishing Vista, and just aren’t ready to talk about
what comes next. The vision for a richer storage in Windows is very
much alive. With the new tools for searching and organizing
information in Windows Vista, we are taking a good step towards that
vision.
Why are parts of WinFS going into SQL Server?
We
have a vision around data that guides us we call the "Data Platform
Vision". We’ve been talking with customers about this for some time,
and we have heard consistent positive feedback. It was clear that the
integrated storage and automation features of WinFS will help SQL
Server deliver on the "Beyond Relational" and "Continuous Availability
and Automation" promises of that vision. We decided to focus resources
on delivering these technologies to our customers as part of the Data
Platform Vision in the near term.
Why did Microsoft announce this now after talking about WinFS at TechEd so recently?
When
we were at TechEd, we had not made the decision. Sure, it was under
discussion, but we did not have all the information we needed and we
had not made the call yet. We did share the news as soon as we had the
final word. We could have waited longer to disclose the information and
made the change in plans less of a contrast, but we chose to notify
people as soon as we could. This is why we used the blog and didn’t
fire-up the big MS PR machinery – that takes time.
I commented internally that the response to Quentin's original blog post shows that there has been a discrepancy between what the WinFS team has been working on and what the developer community believes they were delivering. I got to read a draft of this blog post before it went up and it does a better job of stating what has happened with WinFS and even seems to have incorporated some of my feedback. I hope Charles Miller doesn't think this post is also un-blog-like. :)