301–310 of 543 posts
Earlier quoted context omitted.
you kidding?? Knowing what 200MM people are talking about and being able to display them "relevant" ads based upon it is priceless!!
The day I see ads on whatsapp is the day I leave.
Actually you're working for Facebook... and you do it for free!
Separately, 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.
how long does the full migration and setting the digitical ocean box take to do? debating whether i should do that, or just start over with firebase
It'll really depend on your app, and how many features you used at Parse. In most cases, it should be easier than rewriting your entire app with Firebase, but you should carefully look through the guide and make that decision yourself.
Separately, 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.
Kudos to Parse for providing an open source path forward. I know a lot of enterprise users who will only look at fully open source stacks, for a variety of reasons. It's good they are giving users a year to migrate. I expect Couchbase Mobile to see a lot of evaluations as this process plays out. I will be watching to see how the community grows. It looks like the ExportAdapter.js module in parse-server is low hanging…
Agree 100% -- Parse deserves huge kudos for that move.
Ex-Parse customers should definitely check out Couchbase Mobile, which has some functionality overlap with Parse and is already open source with several repos on github:
https://github.com/couchbase/sync_gateway https://github.com/couchbase/couchbase-lite-ios https://github.com/couchbase/couchbase-lite-android
At least you won't have to worry about getting "Parsed".
I will NEVER trust Facebook again to build products! In fact I will stop using their products and I urge you all to do the same!
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.…
[Couchbase Lite architect here, so I have skin in this game] Even better, if you're using an open protocol, you can work with _either_ a hosted back-end or one you own, and move between them pretty easily. HTTP being a good example of course. The problem is that open protocols for general purpose data sync are pretty thin on the ground. Couchbase built our sync architecture on top of CouchDB's replication protocol, w…
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..
Did anybody actually like 3D TV?
One group of developers this is going to affect most are those who used Parse's GCM Server Key for push notifications. Since Parse is probably not going to reveal this key, Android developers using Parse for push will not be able to use their existing GCM push tokens with other services.
It's really hard to build trust when products disappear. Building on top of google is hard for this reason, and Facebook is beginning to look eerily similar. Recall all of the wonderful social graph access that once existed and see, now, the wake of crippled API's where they once lived. Since it is impossible to build everything from scratch, some compromise must be made, but I wonder whether that compromise can reas…
"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.
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).
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.…
"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.