I usually agree that paradigm wars are nonsense, but I must agree with the article. I started with React but I started working on an Angular project 6 months ago and I feel that the OOP style of Angular doesn't fit well with the DOM.
Think about it, DOM elements are declarative and highly composable so our components should mirror that. However to achieve this in Angular you will need to start utilizing @ViewChild and others or dive into the component factory (dynamic components) while in React I can just easily pass the components around and render however I want without needing special features.
I feel like the hard learning curve of Angular is because the framework is trying to fit something OOP into something that isn't OOP and for this reason it needs to provide escape hatches to achieve the flexibility and composability the DOM needs.
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.
I usually agree that paradigm wars are nonsense, but I must agree with the article. I started with React but I started working on an Angular project 6 months ago and I feel that the OOP style of Angular doesn't fit well with the DOM.
Think about it, DOM elements are declarative and highly composable so our components should mirror that. However to achieve this in Angular you will need to start utilizing @ViewChild and others or dive into the component factory (dynamic components) while in React I can just easily pass the components around and render however I want without needing special features.
I feel like the hard learning curve of Angular is because the framework is trying to fit something OOP into something that isn't OOP and for this reason it needs to provide escape hatches to achieve the flexibility and composability the DOM needs.
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.