4 ms·
Outgrowing Meteor is a valid concern. It's intertwined with your backend and db, so it's definitely a lot of work to migrate off of. I just want to make the di
by lopatin 12y ago
Outgrowing Meteor is a valid concern. It's intertwined with your backend and db, so it's definitely a lot of work to migrate off of.
I just want to make the distinction between that and JS frameworks that don't try to own your whole stack. Migrating from Angular is no more painful than migrating from Backbone. They're all frontend frameworks that talk to a rest api. When choosing between React, Backbone, Angular, Ember, etc ... it seems to me that migration effort shouldn't even be a consideration since a complete UI rewrite will be required in any case.
- notastartup 12y agoI find this troubling. Basically, I feel like we are reinventing the wheels 4 or 5 different ways but we are unable to swap out one for the other. Basically, we spend so much time writing the obvious things like CRUD in almost every permutation possible. Like back when visual basic was popular, you could easily pull together an app, here we are trying to make the web browser do things it was never originally designed for, emulating desktop like responsive app but with multiple vendor interests in trying to dominate this market, it's hard to say who to bet on and why because the developer mindshare is fragmented and we waste time trying to figure out how to create a login using Angular.js, Backbone, Ember.js etc., when short while ago you would just write a jQuery ajax or even better, render it on the server side and send it. The whole idea of having to run phantom.js to render your website because search engine robots can't index your site reminds me awfully like trying to keep up with a high maintenance girl who is more trouble than she's worth.