And I was having such a great day until I read this. R.I.P. Parse
Why? No plans to let it rest.
Facebook buys Parse
91–100 of 288 posts
Re: Facebook buys Parse
#92Damn. I was going to use Parse for my app, but now I will not. What are some of the alternatives out there?
There's UserGrid, which is open source: https://developers.apigee.com/app-services
Re: Facebook buys Parse
#93Earlier quoted context omitted.
That's not really fair. Google seem to work very hard to provide a first class iOS experience on their own services. No reason to assume they'd shut that down on something they acquired.
Well, 1. They shut down their acquired companies and their products on many occasions that many people are dependent upon 2. They shut down a handful of Google tools many people are dependent upon 3. They even close people's Google accounts. Use their service, yes, but trust them after all of this dents they made? maybe. The weight of their actions is so great, I can't even begin to talk about matters in relation to…
Oh, this. Shutting down services is different to restricting services to your own platform. Perhaps you have a point, perhaps Google would hypothetically have decided to shut down Parse had they acquired it, but it's not fair to suggest they'd have limited it to Android.
Re: Facebook buys Parse
#94Whoa. This is pretty big news. This + Piecable + Facebook's huge push in mobile development recently = Facebook building a new, simpler development platform/environment for mobile apps? This speculation can be taken pretty far.
Facebooks problem is a fundamental development culture one, 'move fast and break things' is not great from the perspective of developers latching onto your platform. If the reward is great enough, yes its worth it...
Working on improving these things! Indeed we hope this deal demonstrates that.
Re: Facebook buys Parse
#95As a Parse user I had hoped they would be a "never sell" type of company. This news saddens me.
We will likely be migrating off soon.
Re: Facebook buys Parse
#96Earlier quoted context omitted.
> Yes. (at least on iOS, not sure about Android or Win) er, what? It's an afternoon's worth of work, involving basic PKI and TCP sockets. I know it's an afternoon's worth of work, because I've done it in an afternoon.
It's still an afternoon's worth of headache. Parse is just the time it takes to set up the certs, profile and configure your app. Plus, doing it DIY means you have to maintain a system for sending the notifications, whereas Parse provides that for you.
It also means you own the system, don't get screwed over when Parse gets bought, and all for just a little bit of work.
Seems like a small amount to pay for something that will essentially run itself indefinitely.
Re: Facebook buys Parse
#97This doesn't surprise me in that it seems like a natural fit for Facebook, who has a Mobile Problem [tm]. As much as people fear Facebook becoming The Internet (in the AOL sense), Facebook is actually really late to this party. Apple has a mobile OS, a content and payments ecosystem and a deeply integrated set of products. Google has a mobile OS, GMail, a search engine, a burgeoning content ecosystem and its Maps/loc…
Ironic that Google seems to have a social networking problem, while Facebook has a mobile problem.
If google keeps ramming their social network product down peoples throats it won't be very long before they have more than just a social networking problem.
Re: Facebook buys Parse
#98Damn. I was going to use Parse for my app, but now I will not. What are some of the alternatives out there?
There's a comprehensive list of BaaS providers here -> http://www.kinvey.com/backend-as-a-service
Re: Facebook buys Parse
#99Earlier quoted context omitted.
> Yes. (at least on iOS, not sure about Android or Win) er, what? It's an afternoon's worth of work, involving basic PKI and TCP sockets. I know it's an afternoon's worth of work, because I've done it in an afternoon.
That's silly. Seeing as how I had to google PKI to see what it was, I doubt I'd be able to build a Parse-like service in one afternoon. Parse may not be strictly necessary, but it's a fantastically easy and cheap way for iOS (and Android and front-end and Windows Phone) developers to get their backend up and running.
> Seeing as how I had to google PKI to see what it was, I doubt I'd be able to build a Parse-like service in one afternoon.
Then it's something you would learn, and those several afternoons would mean that you'd be well equipped to tackle a similar problem in an afternoon later.
Basic x509 certificates and PKI is really something an iOS developer (or any developer, really) should be able handle. Understanding this stuff is pretty central to just about all secure communications we have between clients/servers anywhere. It's not like you have to reimplement a crypto library; you just need to know the basics of how they work.
Re: Facebook buys Parse
#100Earlier quoted context omitted.
you laid down an excellent foundation and then just dismissed it on the conclusion. why does buying parse makes perfect sense for facebook? you already mentioned they are doing fine there, with their little piece of the internet in their app. why would they want to support 60,000 apps that does other things out of their little corner? ....oh, will they bait and switch them? all 60,000 apps forced to login via faceboo…
straight off the parse blog: > Q: Will Parse apps have to use Facebook functionality? No.
Promises made just post acquisition have historically had a low correlation with future events.