I give a tremendous amount of respect though to the Parse team for open sourcing the server. Like holy crap they released their entire code base. It must have been especially tough since you have to go through it and clean everything up. Too bad they didn't include the commit history (I certainly understand why they did it). Commit histories are generally the most interesting.
Facebook is closing Parse
81–90 of 543 posts
Re: Facebook is closing Parse
#82Maybe its not such a good idea after all to code your app to a proprietary API in the cloud.
…except that this just has just become an open-source API that is self-hosted?
Re: Facebook is closing Parse
#83Re: Facebook is closing Parse
#84Currently 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.
Re: Facebook is closing Parse
#85Re: Facebook is closing Parse
#86Odd. The Parse SDK had a new release one month ago : http://techcrunch.com/2015/12/14/parse-launches-sdk-support-... That makes this decision seem very sudden.
What the hell is going on?
Re: Facebook is closing Parse
#87Re: Facebook is closing Parse
#88Wow. The 30 minutes you saved by using parse turns into a major headache. This makes me hesitant to use react and react-native.
I'd be hesitant to use anything released by a large company that they don't use themselves for their flagship product(s). Angular 1 comes to mind. I believe Facebook does use React for facebook.com, but not React Native for anything in production yet.
Re: Facebook is closing Parse
#89Re: Facebook is closing Parse
#90Wow. The 30 minutes you saved by using parse turns into a major headache. This makes me hesitant to use react and react-native.