That was unclear. The reason I grouped the dropbox API in there is that it is an HTTP REST API. Good for a lot of things, but to layer a filesystem on top of it is complex and doesn't fit well.
It's a natural extension but it's reinventing the wheel poorly. That happens all the time as things progress. Wheels are reinvented on the new platforms. Normally the new method either pulls ahead quickly or is replaced by an update of the old one. I don't think a good enough implementation of a filesystem over HTTP is easy, and it will at least have to be bloated. A good web aware wrapper around existing filesystem sharing stuff would be much better, sooner of later someone will do that or something even better because they're so clever.
tldr; I like the idea of API's and having internet aware applications for things a browser isn't suited for, and non-http protocols for the things HTTP isn't well suited for. This API strikes me as a poor direction for major development on top of, but makes sense since dropbox is already there and useful.
It's a natural extension but it's reinventing the wheel poorly. That happens all the time as things progress. Wheels are reinvented on the new platforms. Normally the new method either pulls ahead quickly or is replaced by an update of the old one. I don't think a good enough implementation of a filesystem over HTTP is easy, and it will at least have to be bloated. A good web aware wrapper around existing filesystem sharing stuff would be much better, sooner of later someone will do that or something even better because they're so clever.
tldr; I like the idea of API's and having internet aware applications for things a browser isn't suited for, and non-http protocols for the things HTTP isn't well suited for. This API strikes me as a poor direction for major development on top of, but makes sense since dropbox is already there and useful.