[ChristianBundy]

Angular is _fine_, but it's largely a "me too" framework that brings nothing new to the table. On the other hand, it insists on using a non-standard language, which breaks all of the tooling used in the rest of the JS ecosystem.

React and Vue are reasonable options, but as someone using Angular in production I'd urge you to stay far away from Angular and TypeScript.

[veidr]

You're entitled to your opinion, but for many people (me being one) first-class TypeScript support is absolutely a compelling feature.

I may not choose Angular for every project, but I would certainly never again use untyped JavaScript over TypeScript, for an app of any size, unless there was some unusual and very compelling reason.

(And it would have to be a really unusual reason; I can't even think of a hypothetical one.)

In my own experience, TypeScript is a huge advance over JavaScript without types, in both productivity (how quickly functionality gets implemented) and reliability (how many bugs ever make it all the way to a customer).

I will spice up that factual statement with a bit of speculation that will perhaps be more controversial: in my experience watching other developers move to TypeScript, I think the productivity and reliability gains generally apply to their work too, whether or not they personally like TypeScript.

[shusson]

> as someone using Angular in production I'd urge you to stay far away from Angular and TypeScript

Say what you will about Angular, but why the hate on TypeScript? I've found using TypeScript one of the better experiences I've had in the Angular ecosystem.

[jrs95]

I understand the Angular part but why Typescript?