Rants Tagged with “WinFS”
<< < 1 2 (Total Pages: 2/Total Results: 15)
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...
I've been spending some time playing with WinFS lately, and I simply cannot wait until there is real support for making your own types to store. I hope that with the real beta that WinFS will be more fully functional. I can see some impressive things that you could do with WinFS by using it as a local data store. Not just a local data store, but one that can interact with everyone else's data. I'll be reporting more regularly on my WinFS observations in the coming weeks.
I have added a comment to Mike Deem's Blog about the ObjectSpaces issues. Take a look...
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.
