Live data from Hacker News

Facebook is closing Parse

blog.parse.com

31–40 of 543 posts

Re: Facebook is closing Parse

#31
post #3

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

I would amend this to say "its not such a good idea after all to code your app to a proprietary API in the cloud without a plan B"

Re: Facebook is closing Parse

#32

It's really hard to build trust when products disappear. Building on top of google is hard for this reason, and Facebook is beginning to look eerily similar. Recall all of the wonderful social graph access that once existed and see, now, the wake of crippled API's where they once lived. Since it is impossible to build everything from scratch, some compromise must be made, but I wonder whether that compromise can reas…

"Since it is impossible to build everything from scratch.."

Impossible how? If anything, web/api dev has become way easier than it was 10 years ago.

Re: Facebook is closing Parse

#35

It's really hard to build trust when products disappear. Building on top of google is hard for this reason, and Facebook is beginning to look eerily similar. Recall all of the wonderful social graph access that once existed and see, now, the wake of crippled API's where they once lived. Since it is impossible to build everything from scratch, some compromise must be made, but I wonder whether that compromise can reas…

What's even more ridiculous is that their homepage says: From startups to the Fortune 500, hundreds of thousands of developers *trust us*. Trust you to what? Pull the rug out at some point? Why they even put that word on the HP is a separate question.

The acquisition happened nearly 3 years ago. To their credit, they kept running it for longer than a lot of other companies would have.

Anyone in the situation of seeing their platform provider acquired should see the writing on the wall. It's unfortunate, but it's the reality. Enjoy the continued services while [if] they last, but always have a Plan B.

Re: Facebook is closing Parse

#36
post #3

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

... or a walled garden like iOS. But of course people will keep doing it, and keep complaining when the inevitable happens. https://xkcd.com/743/

The walled garden has nothing to do with this.

Re: Facebook is closing Parse

#37

It's really hard to build trust when products disappear. Building on top of google is hard for this reason, and Facebook is beginning to look eerily similar. Recall all of the wonderful social graph access that once existed and see, now, the wake of crippled API's where they once lived. Since it is impossible to build everything from scratch, some compromise must be made, but I wonder whether that compromise can reas…

What's even more ridiculous is that their homepage says: From startups to the Fortune 500, hundreds of thousands of developers *trust us*. Trust you to what? Pull the rug out at some point? Why they even put that word on the HP is a separate question.

The extension of that sentence, when related to Facebook, is "dumb f*cks".

https://en.wikiquote.org/wiki/Mark_Zuckerberg

Re: Facebook is closing Parse

#38
post #30
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.

Why does your user care what API you use?

Re: Facebook is closing Parse

#40
It always sucks when things have to come to an end, however, this is a pretty graceful shutdown if you ask me. Many other service providers, especially in other industries, would often times send you a letter with a month, sometimes less, notice.

From a business learning experience, I'm really interested in the reasoning. I'm hoping a detailed blog post comes out of this, which I'm sure it will, just as a "case study" of sorts.

Post reply on HN