DOM and OOP is futile compared with the Framework vs Library discussion.
Having a robust environment with the Angular CLI is not comparable with the mess that you can have on big projects if you don't have clear standards/architecture in a React project. Angular sets up the initial architecture which will save you time and headaches in the future.
Also the variety of React libraries has trade-offs in the long term. How many initiatives of routing or w/e feature you pick in the community are dead after some time and you have to migrate to another third-party library? oh no, OOP is not the issue here, and @zyulyamba doesn't seem to grasp the magnitude of the stability of both ecosystems.
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.
DOM and OOP is futile compared with the Framework vs Library discussion.
Having a robust environment with the Angular CLI is not comparable with the mess that you can have on big projects if you don't have clear standards/architecture in a React project. Angular sets up the initial architecture which will save you time and headaches in the future.
Also the variety of React libraries has trade-offs in the long term. How many initiatives of routing or w/e feature you pick in the community are dead after some time and you have to migrate to another third-party library? oh no, OOP is not the issue here, and @zyulyamba doesn't seem to grasp the magnitude of the stability of both ecosystems.