News for hackers. Stuff that matters.
Re:Facebook is closing Parse by subpixel on Thursday January 28, 2016 @05:12PM (#10991828)
I'm building on top of Firebase at the moment, and this is exactly the sort of thing I'm afraid of.
Re:Facebook is closing Parse by mayop100 on Thursday January 28, 2016 @06:44PM (#10992454)
[Firebase founder here]

Google is 100% behind us, and we're continuing to make big investments in the platform. If you have concerns, feel free to ask me questions on twitter: twitter.com/startupandrew

Re:Facebook is closing Parse by henrify on Thursday January 28, 2016 @10:48PM (#10993348)
And Facebook was 100% behind Parse, just short time ago.

If anything Google is probably THE most aggressive company in discontinuing products: https://en.wikipedia.org/wiki/List_of_Google_products#Discon...

Re:Facebook is closing Parse by teebot on Thursday January 28, 2016 @05:16PM (#10991858)
I'm afraid google will kill firebase too. I built some sort of mvp with firebase and I intend to port it to express/postgres.
[dead]
Re:Facebook is closing Parse by jaxondu on Friday January 29, 2016 @04:38AM (#10994348)
Too many spam posts from you about Couchbase Mobile. Anyway I do not see the similarity. Parse is hosted platform, build for mobile developers that do not want to self-host the backends, with affordable entry cost. Couchbase Mobile is a product offering with licensing and paid subscriptions for support, pricing has to be requested in order to know the exact, and the backends (Couchbase Sync Gateway and Couchbase Server) starts few thousands dollars per node. And we have to deploy and host the backends (whether we choose to buy or use the free community version). One can choose IBM Cloudant to host, but then Cloudant is hosting CouchDB compatible database and you'd miss the Couchbase Sync Gateway component, which is the main selling points (sync, offline) of Couchbase Mobile. Correct me if wrong.
Re:Facebook is closing Parse by bsaul on Thursday January 28, 2016 @06:14PM (#10992294)
i used to be scared using app engine, but this was for start ups that really couldn't afford using anything else. They gained so much time and saved so much money, it was worth the risk.

But firebase ?? Unless you need real-time capabilities at the DB level, i really don't see the point.