Live data from Hacker News

Facebook is closing Parse

blog.parse.com

241–250 of 543 posts

Re: Facebook is closing Parse

#242

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 se…

Did you check out CloudBoost.io? Its an open platform on Docker + also available as a managed service.

Can someone tell me why this was downvoted? I couldn't find anything wrong with cloudboost.io except for the absence of a Dockerfile in their dockerhub repo.

[edit] Oh, because of spamming. Nevermind.

Re: Facebook is closing Parse

#243

Suddenly, Apple's CloudKit doesn't seem so unattractive - but at the same time I fear it will face a similar fate. Anyone have any insight about whether it's "safe" to build upon? Is there yet an Android solution for connecting to their REST API?

AFAIK, the new Photos app in iOS and OS X are built on CloudKit. So I assume it will only die when iOS dies, which could be another decade or so.

Well, that's not much reassurance because they stopped publicly selling/supporting WebObjects long before they stopped using it themselves.

Re: Facebook is closing Parse

#244
post #203
post #198

A few thought : 1/ parse wasn't a core service for facebook, nor a relevant source of a revenu AND their API wasn't standard. Those points combined made it very risky for people to use it. 2/ since they open sourced their API now, and the service was a paid service, there's a very high probability that someone will very soon create a 100% compatible PAAS. 3/ firebase will be next to shutdown. Not because they suck, b…

Firebase disagrees with you https://twitter.com/Firebase/status/692845862527995904

To be fair, would they say anything else? Even if Google had plans of shutting them down in 3 months, it's not like they'd come out and say, "Oh, we'll be joining parse next quarter."

Re: Facebook is closing Parse

#245
post #198

A few thought : 1/ parse wasn't a core service for facebook, nor a relevant source of a revenu AND their API wasn't standard. Those points combined made it very risky for people to use it. 2/ since they open sourced their API now, and the service was a paid service, there's a very high probability that someone will very soon create a 100% compatible PAAS. 3/ firebase will be next to shutdown. Not because they suck, b…

> gaming console maker (aka Sony) will have the lion's share of the gaming market

Given that you need a bleeding-edge $1000 PC to run Oculus at a smooth, nausea-free 70hz, I don't see how Sony is going to get similar performance from a 2-year-old $400 console.

Maybe a couple generations down the road, but not in the next few years.

Re: Facebook is closing Parse

#248

Earlier quoted context omitted.

sigh, I just made my first app on Parse and now I have to migrate to another BaaS. what do you recommend? Firebase? I dont' think running my own servers with Parse is viable as Parse won't be updated from now on while other BaaS will stay updated and keep improving

Firebase is good for small hackathon-like projects and it gets ugly when your DB grows. Not much optimizations you can do.

[Firebase founder here]

We'd love to know what limitations you've run into and how we can do better! Send me a tweet: @startupandrew

Re: Facebook is closing Parse

#249
post #54

Earlier quoted context omitted.

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

Also many (the majority?) of Parse users signed up with them so that they wouldn't have to self host anything .

yes. Meaning there is a market to fill. Too small to be of interest to Facebook, but I'm sure people will build business upon the open source server.

Re: Facebook is closing Parse

#250
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.

would like to see some tutorial how to move parsedb&server to digitalocean or heroku
Post reply on HN