Facebook is closing Parse • Hacker News Board

Re: Facebook is closing Parse

#21

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

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

Re: Facebook is closing Parse

#22

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

They were kind enough to release a compatible server for users to migrate to their own infrastructure to.

Re: Facebook is closing Parse

#23

Post by chrisfosterelli » Thu, Jan 28, 2016, 10:09 PM UTC

While I'm sure this sucks for a lot of people, I'll be honest the shutdown seems pretty fair. One year notice, detailed migration path with accompanying migration tools, and an open source release of the product itself.

I didn't use parse, but this seems like a reasonable way to do it.

Re: Facebook is closing Parse

#24

Post by minimaxir » Thu, Jan 28, 2016, 10:09 PM UTC

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.

Re: Facebook is closing Parse

#25

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

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

Re: Facebook is closing Parse

#26

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

TamDenholm wrote: post #14

I just started developing something in parse in the last 2 months, i really really liked the platform, this totally sucks. Does anyone have any recommendations for alternatives with similar features?

Running their open source parse platform server on your own infra?

Re: Facebook is closing Parse

#27

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

> There is no such thing as "proprietary API".

I see you are unfamiliar with Oracle v. Google.

Re: Facebook is closing Parse

#28

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

TamDenholm wrote: post #14

I just started developing something in parse in the last 2 months, i really really liked the platform, this totally sucks. Does anyone have any recommendations for alternatives with similar features?

They open sourced an API server that is fully compatible that you could host yourself http://blog.parse.com/announcements/introducing-parse-server...

Re: Facebook is closing Parse

#29

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

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 suppose...

Re: Facebook is closing Parse

#30

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

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