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

111–120 of 543 posts

Re: Facebook is closing Parse

#111

Post by chrstphrhrt »

DocSavage wrote: post #51

And just when I was about to choose between Parse and Google's Firebase. Makes me wonder if Firebase will follow the same path through acquisition, seeming stability, followed by closing? As far as similar open-source systems, it seems like Mozilla's Kinto compares favorably to Parse after it's code is released: http://kinto.readthedocs.org/en/latest/overview.html There's a nice table there comparing the different se…

Whoah Kinto looks cool. Thanks for pointing that out.

I'm one of the Ramses devs http://ramses.tech and we've been working on related problems from an "executable spec" angle.

Seems backend automation is about abstracting storage/syncing and also about making development fast and accessible to different skill levels.

Re: Facebook is closing Parse

#112

Post by carsongross »

This is in no way to dog on Parse, which is handling the situation as well as any company I've seen, but I can't help but think of the hilarious line from https://medium.com/@wob/the-sad-state-of-web-development-160...:

"A [Single Page App] will lock you into a framework that has the shelf life of a hamster dump"

Seems like that could be said about a lot of infrastructure services out there as well.

Re: Facebook is closing Parse

#113

Post by microcolonel »

gfosco wrote: post #2

Separately, we developed an open-source Parse-compatible API server for Node/Express. https://github.com/ParsePlatform/parse-server This, along with the database migration tools released earlier, allow developers a full migration path to move from Parse hosted data + API to their own infrastructure. Over the weekend, I set up a website & app on a $5 DigitalOcean box running Parse and Mongo locally.

Alternate title: “Facebook is opening Parse”

Re: Facebook is closing Parse

#115

Post by simscitizen »

gdeglin wrote: post #48

One group of developers this is going to affect most are those who used Parse's GCM Server Key for push notifications. Since Parse is probably not going to reveal this key, Android developers using Parse for push will not be able to use their existing GCM push tokens with other services.

The easiest way to deal with this is to add your sender ID to the app manifest, so Parse registers with both its sender ID and yours:

https://parse.com/docs/android/guide#push-notifications-sett...

This requires a new release of your app, but that is a necessity in any case.

Re: Facebook is closing Parse

#117

Post by ravenkat »

mmanfrin wrote: post #78
dantiberian wrote: post #47

I wonder if Firebase will be next? They were acquired by Google in 2014. However they also acquired Divshot to join the Firebase team in 2015 which indicates they at least intended to continue with it then. Firebase does at least make more sense as part of Google's cloud services division rather than at Facebook.

I think Firebase's position is a bit more defensible -- Google has done well to ingratiate Firebase as a backend for angular apps.

The news i have heard from various googlers is, `GOOG acquired Firebase because a project started using Firebase as backend and grew very fast and they didn't want to migrate and just acquired FireBase`.

Re: Facebook is closing Parse

#118

Post by cakoose »

minimaxir wrote: post #24

Odd. The Parse SDK had a new release one month ago : http://techcrunch.com/2015/12/14/parse-launches-sdk-support-... That makes this decision seem very sudden.

I have no knowledge of what happened at Parse but based on other experiences I've had, a "sudden" shutdown could be a sign of things being done correctly.

Too often, products are in an extended state of limbo. Internally, the company has given up on it but has been dragging its feet on making the decision to shut it down (or just slow about making the decision public).

As a user, I like to know ASAP if a product I use is probably being killed.

From the company's perspective, keeping a product around half-assedly will probably lead to a slow death anyway; just kill it quickly.

Re: Facebook is closing Parse

#119

Post by blasphemous »

Kudos to Parse/Facebook for a somewhat graceful exit.

However, i find it extremely foolish to shut this down completely from Facebook's point of view.

Sure redeploy all the gun developers to other FB products, but you can't tell me FB could not afford to hire some devs to maintain this service. They could have sold the service to another company too.

This just gives Facebook more bad vibes from the dev community.

Re: Facebook is closing Parse

#120

Post by adventured »

heraclez wrote: post #86
minimaxir wrote: post #24

Odd. The Parse SDK had a new release one month ago : http://techcrunch.com/2015/12/14/parse-launches-sdk-support-... That makes this decision seem very sudden.

And that's not all. Parse just did a full rebranding, including a full frontend overhaul of its dashboard. What the hell is going on?

Deals often are on and then off or otherwise not necessarily expected to happen. In the midst of that, services typically and properly tend to push forward with what they were already doing as though no deal is going to happen. The worst thing you can do, is halt your progress during a negotiation.
Post reply on HN