Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Facebook is closing Parse

blog.parse.com

Post reply on HN
Print view View original

201–210 of 543 posts

Re: Facebook is closing Parse

#201

Post by mayop100 »

DocSavage wrote: post #51

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…

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

Re: Facebook is closing Parse

#202

Post by hamming »

WoodenChair wrote: post #146

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.

Re: Facebook is closing Parse

#203

Post by akent »

bsaul wrote: 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

Re: Facebook is closing Parse

#204

Post by nodamage »

jshen wrote: post #195
nodamage wrote: post #142

This announcement just underscores the importance of having full control over your backend. Yes, it's more work, but if you're writing apps that seriously depend on backend services, it's simply too much risk to depend on anyone else. Fortunately in this case Facebook offered generous lead time to migrate off Parse.com, but they were not obligated to do so, and other providers might not be so generous in the future.…

"This announcement just underscores the importance of having full control over your backend" I disagree. If using something like this let's you get to market much faster, much cheaper, and find market fit faster/cheaper, then it's worth it. Depending on the need it can take millions of dollars and year(s) of work to then begin working on the actual business objectives.

If you're building a nascent mobile app it probably won't take millions of dollars and year(s) of works to get up and running, regardless of what backend you use.

If you do have a project that will take millions of dollars and year(s) of work to get up and running, I'm going to guess you have much bigger problems than what backend you use, and choosing something like Parse won't help you that much.

Re: Facebook is closing Parse

#205

Post by iheart2code »

brandonmenc wrote: post #50
ape4 wrote: post #3

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

> Maybe its not such a good idea after all to code your app to a proprietary API in the cloud. That's why you write an adapter.

That's exactly what I did. I wrote a wrapper around their REST API. Feeling pretty good about that decision right about now.

Re: Facebook is closing Parse

#206

Post by Danielmy »

dmitriz wrote: post #170
Danielmy wrote: post #108

Hey guys, you can try www.backand.com which gives you anything that parse had to offer and much more. Real time, hosting, DB and server side action is just a bit of what they give you. Oh and the best part, it's free.

Is there anything that can keep backand.com away from the fate of Stackmob ( http://venturebeat.com/2014/02/12/paypal-closing-down-backen... ) and now Parse?

Unlike Facebook, backand main business is being a Baas. It has a lot of developers and fully backed. In addition, Backand's unique feature is that you can get the database connection and the server side configuration any time you want!

Re: Facebook is closing Parse

#207

Post by fnayr »

If you're making (mobile) games and looking for a replacement, I cannot recommend Gamesparks[1] highly enough. Their documentation is way behind Parse's (which has excellent docs), but their features (relevant to games) and customer support are far superior, and they are actively working on improving their docs.

[1] http://www.gamesparks.com/

Re: Facebook is closing Parse

#210

Post by simpfai »

intellegacy wrote: post #183
elcct wrote: post #145

I always thought of Parse as a service for someone too lazy to setup mongodb. But to be serious, I think that was a nice tool to get ideas up and running for testing purposes. Running in production? Hell no.

What would you recommend? Im' a new app developer. Debating whether I should begin using Firebase or .. what you just said. The thing is, there are articles guiding me through using Firebase. I'm not sure there are articles telling me how to setup mongodb and where

I guess it depends on what your aims are. Are you new to mobile development in general and just want to learn how to develop for your preferred platform(iOS, Android etc..)? If thats the case then definitely use Firebase or any other backend as a service for that matter. This will allow you to focus on building your app and not have to worry about implementing an API that provides access to your mongodb database(this would also be a worthwhile exercise). Hope that helped.
Post reply on HN