News for hackers. Stuff that matters.
Re:‘Firebase’ Does for Apps What Dropbox Did for Docs by jerguismi on Thursday April 12, 2012 @09:53AM (#3832278)
I don't really get the benefits. You don't need servers, but you need to host the JS/html5 application somewhere, even if you don't need to configure the database server etc.

It is nice technology, but I don't really see if it is worth the price (vendor lock-in, technology lock-in, etc.)

Re:‘Firebase’ Does for Apps What Dropbox Did for Docs by jamest on Thursday April 12, 2012 @10:29AM (#3832425)
Hosting can be handled much more efficiently / easily by someone designed just for content distribution, like a CDN. Our own site is 100% server from a CDN, which makes for very nice scaling characteristics. Also, it's free right now...
Re:‘Firebase’ Does for Apps What Dropbox Did for Docs by haberman on Thursday April 12, 2012 @12:03PM (#3832924)
Or with a scheme like Chrome Apps, the browser could store the app locally. The app could work offline and only use the server to sync/collaborate.
Re:‘Firebase’ Does for Apps What Dropbox Did for Docs by sawyer on Thursday April 12, 2012 @12:11PM (#3832979)
Assuming you know how to build and deploy servers; what advantages would Firebase bring over say: a Socket.IO client -> NodeJS server setup where data was being stored and fetched from memory (Redis or some other data-store)?
Re:‘Firebase’ Does for Apps What Dropbox Did for Docs by SpiderX on Thursday April 12, 2012 @01:37PM (#3833391)
Nothing, I guess... except perhaps scalability.