Facebook is closing Parse • Hacker News Board

Re: Facebook is closing Parse

#401

Post by hanspeter » Fri, Jan 29, 2016, 6:33 AM UTC

abiox wrote: post #312

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.

"the users" are at "a proprietary API"? this seems like a curious notion.

He likely misunderstood everything and is talking about the Facebook Platform ATI.

Re: Facebook is closing Parse

#402

Post by elkhourygeorges » Fri, Jan 29, 2016, 6:38 AM UTC

Why did they do this?

Parse was on track to disrupt the cloud. Why do you need a full backend when you can easily define APIs and access them through mobile and web?

Re: Facebook is closing Parse

#403

Post by mikaelmorvan » Fri, Jan 29, 2016, 6:43 AM UTC

If you want to move to an other BaaS, ZetaPush provides NoSQL as a service, File storage as a service, Search as a service and lot's of other things for mobile, web, server and IoT

Re: Facebook is closing Parse

#404

Post by Startups411 » Fri, Jan 29, 2016, 6:47 AM UTC

spdustin wrote: post #196

I hate to be "that guy", but I use their analytics too, along with in-app push notifications that can be targeted to groups of users. Anyone have experience and recommendations for alternatives that are just as easy to implement in an iOS or OS X app?

I use Google Analytics, Flurry Analytics, Facebook Analytics and Fabric all with custom events. Fabric is great for real-time. Mixpanel seems to be extremely costly depending on what type of app or game you have.

For broadcast push notifications, I use PushWoosh. They have a lot of features that Parse Push doesn't for broadcast notifications.

As for the in-app client-based push notification triggered by liking or commenting on a post or profile, I have no idea how to replace that without Parse. Hopefully they'll included some sort of guide to help with that migration.

Re: Facebook is closing Parse

#405

Post by DannyBee » Fri, Jan 29, 2016, 6:52 AM UTC

aikah wrote: post #319

mayop100 wrote: post #201

Earlier quoted context omitted.

[Firebase founder here] We're not going anywhere. We have strong backing here at Google and are continuing to make big investments in our platform. You'll see big things from us soon. What makes us different? Firebase is very complementary to Google's other product offerings. Cloud for one, as well as Angular, Polymer, GCM, etc.

"We're not going anywhere." I'd like another answer like. "We are thinking about providing a community version that one can deploy on its own servers, then we provide the IaaS when the customer might want to scale". If Parse had an opersource version to begin with, it would have been much much more successful and people would have been less worried about building on a third party platform. If Firebase closes tomorrow…

"Google is a big org. Tomorrow some upper executive you don't even know might decide your product doesn't add value anymore. You know that. "

This demonstrates a pretty strong misunderstanding of how google actually works.

Re: Facebook is closing Parse

#406

Post by profmonocle » Fri, Jan 29, 2016, 6:56 AM UTC

gusmd wrote: post #95

steffan wrote: post #20

Earlier quoted context omitted.

Providing developer services is not Facebook's core business.

Why buy it, then?

I'm wondering that too. If it was just for the talent or a certain technology they probably wouldn't have waited so long to shut it down.

Re: Facebook is closing Parse

#407

Post by patkai » Fri, Jan 29, 2016, 7:03 AM UTC

Kudos to the Parse team for many things, including a much more decent exit than many others. But aside all my admiration for all their achievements - all beyond my abilities - let me ask you, hackers of the world, is this what we really want, if/when we build something so awesome? I do prefer to hear DHH talk stuff like "Basecamp is my life's work".

Re: Facebook is closing Parse

#408

Post by manishkungwani » Fri, Jan 29, 2016, 7:04 AM UTC

My thoughts on the closure, and options moving forward. http://mk.bloomcs.com/parse-com-is-dead/

Re: Facebook is closing Parse

#409

Post by crudbug » Fri, Jan 29, 2016, 7:13 AM UTC

microcolonel wrote: post #113

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”

This would have changed the dynamics a whole lot. Opening up everything and running an instance on parse.com

Re: Facebook is closing Parse

#410

Post by lacker » Fri, Jan 29, 2016, 7:15 AM UTC

wesleyfsmith wrote: post #326

lacker wrote: post #64

Earlier quoted context omitted.

The NYT article has some pretty good explanation here. http://bits.blogs.nytimes.com/2016/01/28/facebook-to-shut-do... "Facebook also would have had to invest untold millions of dollars in capital and, more importantly, engineering talent, to get the Parse business fully off the ground to have a better chance at making a dent in competitors like Amazon, Microsoft and Google." That old blog post doesn't make sense any…

Must have been really hard shutting down your baby. Do you wonder what could have happened if you hadn't sold?

I do wonder, but it's just impossible to know. Working on a startup, there are just so many variables out of your control or understanding. You can't predict what will happen. You can only aim at a vision and do your best to get there.