Re:The present/future of AngularJS
by lhorie on Thursday October 23, 2014 @01:13PM
(#8499332)
The Reddit link seems much less objective than Pete Hunt's overview (e.g. the last point about React not providing code modularity is flat out wrong)
I wrote a frontend framework comparison essay here ( http://lhorie.github.io/mithril/comparison.html ). It's focused heavily on Mithril.js, but might be useful for someone evaluating frameworks.
FWIW, I've used Angular extensively for the past few years and some of the reasons I wrote Mithril (which has a virtual-dom based engine like React) were because 1) Angular performance issues are really hard to fix, 2) I feel some of the design decisions in Angular are fundamentally flawed.
Re:The present/future of AngularJS
by simplify on Thursday October 23, 2014 @02:27PM
(#8499827)
Thank you for writing Mithril; it's a breath of fresh air coming from the complexity of Angular. Not to mention the small size (5kb!) - that'll be especially useful when we build our JavaScript embed widget.
I wrote a frontend framework comparison essay here ( http://lhorie.github.io/mithril/comparison.html ). It's focused heavily on Mithril.js, but might be useful for someone evaluating frameworks.
FWIW, I've used Angular extensively for the past few years and some of the reasons I wrote Mithril (which has a virtual-dom based engine like React) were because 1) Angular performance issues are really hard to fix, 2) I feel some of the design decisions in Angular are fundamentally flawed.