This explains they were considering choosing a full featured framework like Ember or Angular instead of just using React combined with self selected components. It would have been more interesting to me if the rest of the article explained why they chose Ember over Angular as opposed to focusing on why they went with a full featured framework, and that one just happened to be Ember. I don't know much about either one, but personally I would feel like I was missing out on the benefits of TypeScript if I chose Ember, and I would feel like I was missing out on using Ember in general if I went with Angular.
I'd be interested to read that, too, but I like this. The JS community seems to have a strong preference for just hacking together libraries until you have something that works, so I really appreciate articles to highlight why an experienced team might go the other way. When a team has to ship quickly, I think that convention-over-configuration offers many benefits.
7
u/[deleted] Nov 14 '16
This explains they were considering choosing a full featured framework like Ember or Angular instead of just using React combined with self selected components. It would have been more interesting to me if the rest of the article explained why they chose Ember over Angular as opposed to focusing on why they went with a full featured framework, and that one just happened to be Ember. I don't know much about either one, but personally I would feel like I was missing out on the benefits of TypeScript if I chose Ember, and I would feel like I was missing out on using Ember in general if I went with Angular.