eSkaar
TTCTheo's Typesafe Cult
•Created by eSkaar on 2/10/2025 in #questions
I'm sorry, but angular, react, migration, thoughts?
TLDR: I am working at a company where the codebase is written in the MEAN stack. I have quite a lot of experience with react. We are only a team of 5 devs. How hard is it to migrate the angular code to react? Anyone done a migration like this? Does it make sense to do a migration like this? All thoughts about a big migration like this is highly appreciated! 😃
Rant: Why would i want to do this at all you might ask, well simply because i think angular sucks. Only been using it for a couple of weeks, but simple stuff as editor recognizing types and giving suggest for props is a hazzle in angular. The templating of angular does not give autocomplete or correction for errors, theres a whole list of reasons why i want to abandon the angular ship, but mostly it is because i feel like the angular community is none-existent, it seems to be near dead and it is really hard to find tutorials, ui libraries, discussions, examples and so on. And the thought process and syntax of the system just seems old. Importing a component into a new component means importing the thing twice in one file. Stuff like that is just insane to me. This is adressed in the 2025 strategy for angular, aka RFC for selectorless components - https://blog.angular.dev/angular-2025-strategy-9ca333dfc334, but i dont like the feeling of trusting a promise from google. Google does not have a great record of keeping their promises and keeping products alive. I could go on and on, but in the end i just want input on whether or not this is a crazy idea to suggest to the company. It is a frontend with about 30 pages, and probably about 1000 components, probably about 100K lines of frontend-code.
9 replies