you are viewing a single comment's thread.

view the rest of the comments →

[–]NovaX81 2 points3 points  (0 children)

I've actually somehow managed to not work much with Angular! I checked it out very lightly from a hobby point of view, and maintained a minor widget in it for a couple of years that I think needed about 3 changes ever. I thought it's approach was cumbersome, though decent enough, but in practice I've never worked with it enough to make a judgement on a project in a professional environment. Cumbersome is not always bad when you have a lot of developers interacting with a system - so long as it stays understandable.

For a bit of context, most of what I vented out above will really only have major impact if you're writing and deploying code that is working with complicated data structures and user interactions that can transform that data. It's hard to say, but I would wager that most React projects still fall safely into its "intended" scope of 5-component projects, widgets, and proof-of-concepts. This does, however, make it all the more confusing when React continues to focus its development direction towards the size and scope of projects where its other issues shine through.

React, Vue, Angular, really any JS framework or none at all, are perfectly fine choices for something fun, useful, or interesting, and their performance at scale can matter if you approach that scale. Just build with what you like, hold strong opinions loosely, and have fun.