Benefits of WinFS explained

Another good article from Ray Ozzie, this one called 640K Ought to be Enough for Anyone discussing the potential of WinFS, the storage scheme for the next Windows OS, code-named Longhorn. Well worth reading the whole thing, here is a key clip:

In a pre-WinFS world, each application has managed its own “documents” and “records” and “collections” as an island unto itself – each with its own indexing and interaction mechanisms, each with its own solution-building mechanisms. Good ‘nuf. But in a WinFS world – just like in a Web Services world – we have the opportunity to explore what would happen if we dared to “deconstruct and refactor” our concepts of traditional client-side applications into a mesh of separately-built application components that “meet” at the level of common persistent objects and relationships.

From the WinFS site is this description:

“WinFS” is the code name for the next generation storage platform in Windows “Longhorn.” Taking advantage of database technologies, Microsoft is advancing the file system into an integrated store for file data, relational data, and XML data. Windows users will have intuitive new ways to find, relate, and act on their information, regardless of what application creates the data. Also, “WinFS” will have built-in support for multi-master data synchronization across other Longhorn machines and other data sources.

For more details on WinFS, check out the site.

Ray also goes off on a bit of a tangent exploring the debate between “rich” and “thin” clients. In my experience, many people have a tendency to want one or the other almost exclusively. Of course, what they really want is just a single interface to everything.

Author: gBRETTmiller

I'm not lost, I'm wondering