3 ms·
After using Angular for years at large Blue Chip projects I decided to switch over to React projects to see the other side of the isle for the last 4 years. Th
by woodpanel 4y ago
After using Angular for years at large Blue Chip projects I decided to switch over to React projects to see the other side of the isle for the last 4 years.
The atomicity of React makes it applicable in an immense variety of usecases, however this comes at the cost of an ecosystem providing a very fragile dependency graph.
With React you'll almost always have the newest trendy thing available as a tool (and not with Angular)[1]. Which means if someone comes up with a completely new philosophy that might better match your (team's) mental models, chances are it's available for react first.
OTOH this means chances are that the concensus of "how to do things" has changed so much within a short time, that older projects are not only difficult to upgrade, but consist of code that is really, really hard to understand at all.
[1] e.g. there was a time when Google's own Material UI was better implemented for React than for Angular.