4 ms·
I am really impressed with the direction Parse is taking. It seems to me they are fixing the right problems and they are doing it step by step. One thing I wou
by rudasn 14y ago
I am really impressed with the direction Parse is taking. It seems to me they are fixing the right problems and they are doing it step by step.
One thing I would love to see, is a way (an API) to abstract their Javascript library. I would really like to use another JS library other than their own. That would make the cloud code feature even better for me.
I am wondering how long it will take them to stop marketing themselves as a mobile app platform. They are [becoming] much more than that.
- napoleond 14y agoI haven't had a chance to use Parse yet, so I'm curious: what's wrong with their JS library, and couldn't you use the REST API directly instead?
- mikebridgman 14y agoOne thing I noticed is that their library is essentially Backbone and Underscore, and their docs state that it has all existing functionality...except I keep finding functions that aren't included, so I still have to load my own version of Backbone. But you're right: for my next app, I'll probably just use their REST API directly.
- napoleond 14y agoOdd. I wonder why they didn't just override Backbone.sync.
- shykes 14y agoI think that's exactly what Backlift does: https://www.backlift.com/ https://www.backlift.com/ (I'm not affiliated with them)
- lacker 14y agoThere is some stuff that we want to handle differently, like when you increment a field it is usable locally but maps to an increment operation rather than a set on the server. So for a slew of details like this, overriding Backbone.sync wasn't quite sufficient. I hear the concerns about the trickiness of using plain Backbone with Parse, though - that is a design issue we are thinking hard about.