Facebook is closing Parse • Hacker News Board

Re: Facebook is closing Parse

#51

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

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 services' features.

Re: Facebook is closing Parse

#52

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

My thoughts: http://i.imgur.com/TnQRX6v.gifv

Re: Facebook is closing Parse

#53

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

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'm afraid google will kill firebase too. I built some sort of mvp with firebase and I intend to port it to express/postgres.

Re: Facebook is closing Parse

#54

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

zenojevski wrote: post #25

ape4 wrote: post #3

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

…except that this just has just become an open-source API that is self-hosted?

Luckily, this time. Not all startups who provide a service like this may choose to do the same when they implode.

Re: Facebook is closing Parse

#55

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

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.

[deleted]

Re: Facebook is closing Parse

#56

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

will you also open source the front end tools? i really loved the data explorers

Re: Facebook is closing Parse

#57

Post by eachro » Thu, Jan 28, 2016, 10:17 PM UTC

I used Parse a few years ago to serve as a backend for a simple event aggregation app. It was incredibly simple to use and integrate with. I probably spent on the order of ~1hr reading documentation and another 2 hours doing some quick and dirty implementation before having a functioning Android app. It's too bad it's shutting down, but I can't say I didn't see this coming after the Facebook aquisition.

Re: Facebook is closing Parse

#58

Post by smt88 » Thu, Jan 28, 2016, 10:17 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.

I don't think that's reason enough. AWS wasn't/isn't Amazon's core business, either. For a company that wants to be deeply integrated in all web-connected software, it makes sense to make it as easy as possible for developers to work with them.

Re: Facebook is closing Parse

#59

Post by kuzmin » Thu, Jan 28, 2016, 10:19 PM UTC

Currently using Parse for Push notifications (it's simple to send a request to Parse and it handles iOS vs Android issues).

Is there any tool out there that has similar functionality? Ie. you register all your users devices there and they simplify the sending of push notifications.

Re: Facebook is closing Parse

#60

Post by benwilber0 » Thu, Jan 28, 2016, 10:19 PM UTC

duaneb wrote: post #38

mhurron wrote: post #30

Earlier quoted context omitted.

'Someone once asked Slick Willie Sutton, the bank robber, why he robbed banks. Sutton looked a little surprised, as if he had been asked “Why does a smoker light a cigarette?” “I rob banks because that’s where the money is,” he said, obviously meaning “in the most compact form.”' Why do you develop against a proprietary API? Because that's where the users are.

Why does your user care what API you use?

yeah this makes no sense