Facebook is closing Parse • Hacker News Board

Re: Facebook is closing Parse

#41

Post by subpixel » Thu, Jan 28, 2016, 10:12 PM UTC

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

#42

Post by jaboutboul » Thu, Jan 28, 2016, 10:12 PM UTC

theunquietone wrote: post #4

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.

Fosco, you are awesome and it was a pleasure working with you :)

Hi Ashley! Thank you guys.

Re: Facebook is closing Parse

#43

Post by humanfromearth » Thu, Jan 28, 2016, 10:13 PM UTC

chasing wrote: post #18

Which alternatives would people recommend?

I would recommend Kinto. It's open source and used in production for mozilla browser sync service.

https://github.com/Kinto/kinto

Re: Facebook is closing Parse

#44

Post by [deleted] » Thu, Jan 28, 2016, 10:13 PM UTC

sktrdie wrote: post #21

ape4 wrote: post #3

Maybe its not such a good idea after all to code your app to a proprietary API in the cloud.

There is no such thing as "proprietary API". There are proprietary implementations...

[deleted]

Re: Facebook is closing Parse

#45

Post by u320 » Thu, Jan 28, 2016, 10:14 PM UTC

steffan wrote: post #20

sehr wrote: post #7

Any specific reasons why? Always thought they were doing well, reasonably popular etc

Providing developer services is not Facebook's core business.

So, you're saying we should prepare for the "Oculus shuts down" announcement?

Re: Facebook is closing Parse

#46

Post by chasing » Thu, Jan 28, 2016, 10:15 PM UTC

ape4 wrote: post #3

Maybe its not such a good idea after all to code your app to a proprietary API in the cloud.

Maybe it's also not such a good idea to claim you know everyone else's needs and constraints...

Re: Facebook is closing Parse

#47

Post by dantiberian » Thu, Jan 28, 2016, 10:15 PM UTC

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.

Re: Facebook is closing Parse

#48

Post by gdeglin » Thu, Jan 28, 2016, 10:15 PM UTC

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.

Re: Facebook is closing Parse

#49

Post by hkmurakami » Thu, Jan 28, 2016, 10:15 PM UTC

>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 to see since I saw the Parse acquisition as a beacon for platform companies being able to run independently post acquisition. :(

Re: Facebook is closing Parse

#50

Post by brandonmenc » Thu, Jan 28, 2016, 10:16 PM UTC

ape4 wrote: post #3

Maybe its not such a good idea after all to code your app to a proprietary API in the cloud.

> Maybe its not such a good idea after all to code your app to a proprietary API in the cloud.

That's why you write an adapter.