Hacker News new | ask | show | jobs
by rajeshamara 3210 days ago
No Framework is perfect. There are always tradeoffs. Just because some things didn't work for you doesn't mean you can generalize and say Angular2 is bad. The way the Author wrote, he is generalizing things and making assumptions based on baseless facts
2 comments

I think, unlike the author, I had pretty solid reasons why I didn't like it. Most applications are glorified forms on the front-end and Angular2 has the most rigid and difficult form handling I've used in a web framework.

Form validation is a long-solved problem and doing custom validation is a huge pain. Accessing the raw DOM sets off warning bells but in Angular2 it needs to be done for simple things like form field focus. You need to implement FieldValueAccessor for custom fields and the documentation for that sucks.

There's two different form libraries that are largely incompatible. Underneath that several ways to instantiate and manipulate both types of forms. It's so hard to build practical components that Angular2 Material still isn't finished.

If my company wasn't using ng2 extensively I would jump ship for react asap

Angular 2 is behind React and Vue in developer satisfaction. And the criticisms levied against NG2 are legitimate. They dropped the ball on a lot of things that were solved a long time ago in React.

Vue, on the other hand, has adopted many of the best features of React and responded well to user feedback. I think it's a strong competitor and I can totally understand someone picking Vue over React. I cannot say the same for NG2.