Facebook is closing Parse
311–320 of 543 posts
Re: Facebook is closing Parse
#312Maybe its not such a good idea after all to code your app to a proprietary API in the cloud.
'Someone once asked Slick Willie Sutton, the bank robber, why he robbed banks. Sutton looked a little surprised, as if he had been asked “Why does a smoker light a cigarette?” “I rob banks because that’s where the money is,” he said, obviously meaning “in the most compact form.”' Why do you develop against a proprietary API? Because that's where the users are.
Re: Facebook is closing Parse
#313Re: Facebook is closing Parse
#314Currently 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 just created an account on OneSignal: https://onesignal.com/
Re: Facebook is closing Parse
#315Re: Facebook is closing Parse
#316Separately, 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.
Re: Facebook is closing Parse
#317Earlier quoted context omitted.
"Since it is impossible to build everything from scratch.." Impossible how? If anything, web/api dev has become way easier than it was 10 years ago.
Do you write your compiler from scratch every time you push an update to your web server? Edit: it is turtles all the way down (and the only way it's not impossible is by virtue of standing on the shoulders of giants).
Re: Facebook is closing Parse
#318I chose Parse because it looks better than Firebase... this latest development is beyond me. Such a promising product...
Re: Facebook is closing Parse
#319And 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.
I'd like another answer like. "We are thinking about providing a community version that one can deploy on its own servers, then we provide the IaaS when the customer might want to scale". If Parse had an opersource version to begin with, it would have been much much more successful and people would have been less worried about building on a third party platform.
If Firebase closes tomorrow there will be no migration strategy for people who built their infrastructure around Firebase.
> Firebase is very complementary to Google's other product offerings
Google is a big org. Tomorrow some upper executive you don't even know might decide your product doesn't add value anymore. You know that.