Live data from Hacker News

Facebook is closing Parse

blog.parse.com

361–370 of 543 posts

Re: Facebook is closing Parse

#361

Earlier quoted context omitted.

A few more thoughts: 1. This effectively poisons the well for any other BaaS providers out there. If two of the biggest companies in this space (StackMob and Parse) can get acquired and shut down in less than 5 years, what does that say about the future of the smaller companies in this space? As a developer how could you possibly trust any of these companies going forward, based on this track record? 2. Syncing is no…

Au contraire: it opens a wider deeper well. Parse customers are now up for grabs. Do you think they will go back to program back-ends and rent a server? I personally won't. So the supermaket chain where you usually shop at closes its stores for whatever reason. Do you go back to farming your backyard or do you find a new store? The BAAS industry is super young, only hipsters are into it. But it makes sense so it will…

Switching supermarkets is much, much, easier than switching backends. I'm sure lot more BaaS companies will pop up to grab former Parse customers. I'm not sure how many of those will still be around in another 5 years.

I strongly suspect there's something negative about the economics of BaaS services that's being implied by the fact that two of the most successful providers have shut down after acquisition.

Re: Facebook is closing Parse

#362

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?

Wow - the dashboard looks close to Parse's new dashboard.

https://developer.apple.com/icloud/images/cloudkit-dashboard...

Re: Facebook is closing Parse

#363
post #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.

That completely depends on how graphics intensive a particular game is. Sure you won't be running the Witcher 3 at 90 fps, but it's definitely possible if you make a game that is more stylized and less photo realistic.

They're also apparently using some kind of frame interpolation to run 60hz games at 120hz. How well that works to stop nausea I don't know, but the reviews from early demos I've seen look promising.

Re: Facebook is closing Parse

#365
post #59

Currently using Parse for Push notifications (it's simple to send a request to Parse and it handles iOS vs Android issues). Is there any tool out there that has similar functionality? Ie. you register all your users devices there and they simplify the sending of push notifications.

I'm head of developer evangelism at http://pubnub.com and we can handle push notifications for you easily. What is your use case?

Hey, we are migrating from Parse and planning to use PubNub. With parse, 1. we use channels to subscribe. 2. All the cross platform thingy like iOS/Android/Windows is managed by Parse.

I have a couple of questions.

1. Do you have a way to upload all the channels+device tokes and stuff that we can extract from Parse? 2. What does the "Daily Active Devices" - 100 for Free tier mean? Does it have to do with Push notifications? because we are NOT using it for realtime connections.

We will have about 7-8 thousand devices registered and < 1 million push notifications. So are we still under the Free tier?

Re: Facebook is closing Parse

#366
Parse is a great provider for push notifications, having only really gone down once in the time we've used it (and also being, well, free). I didn't use any other part of the system because we had our own databases and whatnot, but it is great for push. It will be missed.

Re: Facebook is closing Parse

#367

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

100% agree. Building my first notification-based app right now and Parse seemed like the obvious and best choice. Thing is, after a bit of thinking something felt...off. Not with the service, but off with the idea of attaching this small little project to something so...out of my control. I dug around the net and found a working solution I could install on my own server, and now that's exactly what I've got: The expe…

May I ask what that solution was? :)

Re: Facebook is closing Parse

#368

Earlier quoted context omitted.

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.

Pretty sure they still use WebObjects for iTunesConnect (at least).

Re: Facebook is closing Parse

#369
What is Facebook retaining? There must be something they are holding onto. Would it make any sense for FB to give the original founders the option to buy back Parse? With them open sourcing most of the product, what could they still have?

Re: Facebook is closing Parse

#370
I think Parse is an awesome platform and was really well documented. I used it for building my app, and will probably end up migrating to my own parse server and then decide where to go from there.

Parse really made it easy to get an app running. Especially a couple of years ago, when api's were complicated.

I'm going to miss the push notifications, I just implemented them and they work really well. Hopefully an open source solution will get released so we can continue using them.

Post reply on HN