4 ms·
I just spent the full day moving an Angular admin to React and so far, my initial optimism has died down a bit. Yes, Angular has more concepts to learn (most o
by ericclemmons 13y ago
I just spent the full day moving an Angular admin to React and so far, my initial optimism has died down a bit.
Yes, Angular has more concepts to learn (most of which you already know if you've used any complex framework), and custom directives are a mine-field of changing one property at a time until everything finally works, BUT, once everything's working in Angular, maintenance & updates within the existing architecture is quite simple.
So far with React, I've married Backbone.Router + RequireJS + React successfully, but it certainly feels like I'm still writing lots of boilerplate. That is partially RequireJS' fault (I've never cared for the bloat), and the other part how messy my views end up by rewriting much of Angular's "filter"s and "ng-" directives.
- vjeux 13y agoCan you give some examples of filters and ng-directives that you had to rewrite? I found that most of them can easily be translated with underscore functions.
- ericclemmons 13y agoRe-implementing 'filter' & 'orderBy' (especially when reversing) were great examples of extremely common functionality that I eventually abstracted out into React's "Mixins". So, to rephrase, Angular (much like Dojo did over a half-decade ago) gets you 90% there while Backbone (and to a less degree React) puts some of the boilerplate burden back on you. I'm still doing a re-factor trying to figure out the optimal way of using React (we're talking in IRC now!), so I'm not done with it yet! :)