Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It seems like we just need a wrapper that lets you pick whether to use Parse or Backbone. That should eliminate the worry of lock in (you'd still have to add the server code if you convert away from Parse, but you'd have to do that anyway).


For Backbone, wouldn't that just be editing the base URLs of your models?

Edit: Just re-read, I think you meant to say between Rails and Parse -- with Parse, you'd still need Backbone.


Exactly,

A) if you don't use Parse you're going to have to write server code. B) If you do use Parse and decide to change in the future you're going to have to write server code.

The outcome is the same however with option B you will have a working app 70% faster. Parse is great for moving fast while you search for product/market fit.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: