3 ms·
We started in Backbone, then migrated to Angular to mitigate nested view chaos. Latest rewrite drops Angular in favor of React and a bit of Backbone, mostly to
by andyl 13y ago
We started in Backbone, then migrated to Angular to mitigate nested view chaos. Latest rewrite drops Angular in favor of React and a bit of Backbone, mostly to reduce the learning curve for new devs. Using React for views is the simplest/most robust stack we've experienced. Easier to share/reuse code, easier to debug.
React with Coffeescript has been super great - dropping JSX lowers the learning curve even more, especially since we already use and love slim, and Coffee/React sort of resembles slim.
- hamxiaoz 13y agoI'm using Angular and I'd like to try react. Is it easy to transform an angular project to backbone + react? Do you have to use Marionette?
- freyr 13y ago>> then migrated to Angular to mitigate nested view chaos. For the record, and for those who are unfamiliar, "nested view chaos" isn't an inherent characteristic of Backbone, and it can also be mitigated by writing good, thoughtful code (often easier said than done). Using React views can make life easier, since composition of nested components is part of the design.
- oh_sigh 13y agoYeah...I imagine that the original poster is going to be making a very similar post in 1 year, saying "We started in React, but switched to <sexy new tool> because <some fault of our own that we then blame on React>"