Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Facebook is closing Parse

blog.parse.com

Post reply on HN
Print view View original

171–180 of 543 posts

Re: Facebook is closing Parse

#171

Post by avolcano »

btown wrote: post #29

It will be funny to see all of the abandoned apps that start failing a year from now. Obscure games, utilities, etc. Most people won't be bothered to go through the stress of an App Store review process to update an old free-to-play app that's not even making them revenue. But how many people's morning commutes will be ruined when their old games or news apps fall apart? The price of progress (and of liquidity), I su…

To be fair, those exact same abandoned apps would just as easily stop working because their developer didn't upkeep their custom backend - or worse, those abandoned backends could fall behind on security updates and get hacked.

Re: Facebook is closing Parse

#172

Post by hkmurakami »

rms_returns wrote: post #65
hkmurakami wrote: post #49

>We’re proud that we’ve been able to help so many of you build great mobile apps, but we need to focus our resources elsewhere. I read this as "our Facebook overlords have decided that our revenue/head can be dramatically increased if redeployed on a different part of the overall company, so they have decided to shut Parse down and move us elsewhere." Which is a perfectly fair business decision but this is really sad…

If resource is the question, then I wonder how come they are sustaining WhatsApp? Its a zero-profit activity, the users chat amongst themselves, what does FB gain from that? I guess the parse resource traffic would be little compared to terabytes flowing through the WhatsApp every day.

That area of their farmland will eventually harvested to great profits (or at least that is their plan).

Parse was already monetizing and they could see the margins they were getting, and were not satisfied.

Re: Facebook is closing Parse

#173

Post by nodamage »

nawazdhandala wrote: post #150
nodamage wrote: post #142

This announcement just underscores the importance of having full control over your backend. Yes, it's more work, but if you're writing apps that seriously depend on backend services, it's simply too much risk to depend on anyone else. Fortunately in this case Facebook offered generous lead time to migrate off Parse.com, but they were not obligated to do so, and other providers might not be so generous in the future.…

... or use an open source BaaS which can be self hosted or managed like CloudBoost.io

Yes, self-hosting falls under "owning your own backend". The managed option carries the same risk of shutdown as with any other provider. I think you can stop spamming your website in this thread now that you've mentioned it a half dozen times though.

Re: Facebook is closing Parse

#175

Post by bsaul »

subpixel wrote: post #41

I'm building on top of Firebase at the moment, and this is exactly the sort of thing I'm afraid of.

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.

Re: Facebook is closing Parse

#177

Post by lsiunsuex »

wow.

A year ago when I rewrote my startup's product in AngularJS I was on the fence between Firebase and Parse. Built prototypes against both and ended up going with Firebase for a few reasons - 1: price, 2: owned by Google and not FB and 3: the whole 3 way data binding thing.

Awesome to see them releasing code for the backend but I'm finding this trend really disturbing - relying on 3rd party services for everything.

Doesn't anyone remember back in the day (like 5 years ago hah) when programmers / admins actually bought software and ran it on their own servers and didn't "rent" it? I know, crazy right? To own software and if the company went under, things could still be fine for a while longer.

Maybe it's time to consider my use of Firebase and go back to the way things used to be.

Re: Facebook is closing Parse

#180

Post by intellegacy »

nodamage wrote: post #142

This announcement just underscores the importance of having full control over your backend. Yes, it's more work, but if you're writing apps that seriously depend on backend services, it's simply too much risk to depend on anyone else. Fortunately in this case Facebook offered generous lead time to migrate off Parse.com, but they were not obligated to do so, and other providers might not be so generous in the future.…

sigh, I just made my first app on Parse and now I have to migrate to another BaaS. what do you recommend? Firebase?

I dont' think running my own servers with Parse is viable as Parse won't be updated from now on while other BaaS will stay updated and keep improving

Post reply on HN