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

471–480 of 543 posts

Re: Facebook is closing Parse

#471

Post by jsutton »

outworlder wrote: post #295
nocarrier wrote: post #239

Earlier quoted context omitted.

I think you're pretty far off the mark when you say that Oculus is at risk if they don't sell enough devices. Of course, we have to go off of what Oculus and FB says, but they are working to create an ecosystem and market for VR experiences and seem to be pushing VR forward wherever they can; look at Oculus Studio and the work they're doing to create interactive movies, as well as the software deals with partners lik…

Or maybe it will turn out that VR is just a niche market or passing fad (for the Nth time). Or it won't gain the required traction within the FB executive's patience threshold. Both are very likely outcomes. > VR is a huge opportunity and is likely to be the entertainment medium of the future Is it? Last time it was 3D. And before that..

3D TV was a marketing iteration for television.

VR is a revolutionary technology. Much more akin to smartphones. It's not hard to imagine the possibilities that VR can bring.

Re: Facebook is closing Parse

#475

Post by akarve »

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

for most applications i hypothesize that the cost of writing and maintaining your own backend will far outstrip the cost of the occasional migration.

if anything, the pressure is towards frontend:backend isolation, not away from BaaS. (in the spirit of segment.io for analytics.)

one ironic signal here is that money is bad for survivorship. facebook killed parse because it doesn't move the needle for facebook, but parse might have been a fine & profitable standalone business.

Re: Facebook is closing Parse

#476

Post by akarve »

jonsterling wrote: post #216
jshen wrote: post #195

Earlier quoted context omitted.

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

We used Parse, and (contrary to your suggestion) it helped us get to market much slower and much more expensively . We experienced a hilarious amount of downtime, and hundreds of engineering hours that could have been spent developing features for our users or improving our services were spent working around fatal bugs in Parse, which were usually not manifesting on all instances, which made it very difficult for the…

painful. though more an indictment of parse than BaaS. the firebases of the world seem to work better. 20/20 hindsight, when should you have gotten off of parse and why didn't it happen?

Re: Facebook is closing Parse

#477

Post by irox859 »

eru wrote: post #454
tuyguntn wrote: post #431

Earlier quoted context omitted.

Hacker culture of Facebook makes it really valuable company in terms of engineering. Dropbox and Google (Mailbox & Reader at least) should learn something from them. Incredible move and good luck in future endeavors!

Alas, open sourcing Reader wouldn't have done much: the code's all tied heavily into Google internal infrastructure. (Full disclosure: my team pulled the plug on Reader.)

Oh you're the villain!

But yes I can see that as joining a Blogger page in the Members widget automatically subscribed you in Reader.

Re: Facebook is closing Parse

#478

Post by akarve »

jonsterling wrote: post #284
derefr wrote: post #259

Earlier quoted context omitted.

Interesting. Sounds like Parse wasn't nearly as mature as they made themselves out to be. I'd have expected at least PaaS levels of stability—by, at the very least, pinning each client to a particular API version with guaranteed semantics until they choose to shift to making requests on higher-versioned equivalents of each API resource. A thought: if "Parse" had originally just been this open source Parse Server offe…

Thanks for your comment; regarding your thought, from my perspective there was nothing that Parse provided that was easier than just building the app on Heroku ourselves. And we wouldn't have been stuck in the horrible node/javascript ecosystem then! So, I would say, if Parse had been this Parse Server product from the start, that would have been a lot better! But there wasn't really any need for such a thing at my c…

really "incestuous"? firebase is/was a YC company, too. it's sad when cronyism trumps reason.

Re: Facebook is closing Parse

#480

Post by lebnox »

humanfromearth wrote: post #43
chasing wrote: post #18

Which alternatives would people recommend?

I would recommend Kinto. It's open source and used in production for mozilla browser sync service. https://github.com/Kinto/kinto

Here, check out this: http://www.shephertz.com/parse-migration-app42.php
Post reply on HN