News for hackers. Stuff that matters.
Re:WinFS, Integrated/Unified Storage, and Microsoft by geocar on Saturday December 14, 2013 @06:15PM (#6907537)
No it doesn't. And those are important problems, but another very important problem that needs solving is getting everyone to put all of their content into WinFS and make all of their services available from WinFS. Using an existing system bypasses a huge part of that.
Re:WinFS, Integrated/Unified Storage, and Microsoft by dpark on Saturday December 14, 2013 @07:51PM (#6907801)
>Using an existing system bypasses a huge part of that.

Not really. I'm not sure it's any less work to move an entire app to use a new interface than to move to a new file store. Your mail app doesn't implement an HTTP interface that a unified search engine could consume.

Re:WinFS, Integrated/Unified Storage, and Microsoft by yajoe on Saturday December 14, 2013 @08:32PM (#6907910)
Really?

Exchange: http://msdn.microsoft.com/en-us/library/office/jj900500(v=ex...

Gmail: https://developers.google.com/gmail/gmail_inbox_feed (Search is only available publicly via SMTP and IMAP, which technically isn't HTTP, but the Gmail app is clearly using HTTP XHRs)

Re:WinFS, Integrated/Unified Storage, and Microsoft by dpark on Saturday December 14, 2013 @09:34PM (#6908096)
Yes. Gmail and Exchange are not apps running on your system. It's fine to say that remote apps should interface over HTTP, but this doesn't address any local apps that currently use custom data stores, unless the answer is to move everything online, which is a much bigger undertaking than making everyone use a consistent data store.

The HTTP proposal also ignores all the data your apps already have locally. Outlook already has your mail. Why go to the server?

HTTP also doesn't magically make consistent free-form queries work. So again, I don't see how HTTP really accomplishes anything on its own with respect to the goals of WinFS.