3 ms·
I'm not getting this. Fine if you want to go back to the early 90s when sites were all static but what does this model offer for dynamic sites and in particular
by cutler 9y ago
I'm not getting this. Fine if you want to go back to the early 90s when sites were all static but what does this model offer for dynamic sites and in particular sites which are intended to scale beyond a single, home user box? How do I migrate my Rails app to dat/ipfs?
- allannienhuis 9y agoMy understanding is that you can't - the use case isn't for dynamic websites - it's for static content. You could migrate your angular/react SPA (who's front-end is based off of static content), and continue to use the REST / WS services you already have, but not sure what the point of that would be. I think it's better to think of this more as a data store than web sites/apps.
- carussell 9y agoThis is not true. See the remarks about the DatArchive APIs in my original comment. You can also look at Fritter[1], which is a prototype Twitter clone built as a Dat web app. It's true that there are some types of web apps that exist on the traditional (HTTP) web but that cannot be made as a Dat app, but it's also true that there are a class of apps that could be built with Dat but that cannot be built on the traditional web. 1. dat://fritter.hashbase.io