I appreciate your preference in having state management and routing managed by the same team BUT...
I'm afraid, that doing so was a common mistake over the years that is repeated over and over again.
The simple reason is, more tools the team must maintain, less time they have for each of them.
The Angular way of maintaining the whole ecosystem reminds me TV with VHS builtin era.
I think this is the reason why so many people moved from Angular to React recent years.
But there are situations where Angular way is a better one. I think if you work in corporate environment, and you need to vet every package you are using, it's easier to get approval on "batteries included" framework as Angular and go with it, that ask for Mobx, React-router, axios etc. separately.
Also for people who start coding, having a choice made for them can help.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Guiseppe,
I appreciate your preference in having state management and routing managed by the same team BUT...
I'm afraid, that doing so was a common mistake over the years that is repeated over and over again.
The simple reason is, more tools the team must maintain, less time they have for each of them.
The Angular way of maintaining the whole ecosystem reminds me TV with VHS builtin era.
I think this is the reason why so many people moved from Angular to React recent years.
But there are situations where Angular way is a better one. I think if you work in corporate environment, and you need to vet every package you are using, it's easier to get approval on "batteries included" framework as Angular and go with it, that ask for Mobx, React-router, axios etc. separately.
Also for people who start coding, having a choice made for them can help.