I would argue that 8 is not accurate since Angular provides cookie cutter training wheels to architect an application, whereas React gives you the flexibility to do significantly more good and bad with the right experience and skillset in mind.
I would also argue that 10 is slightly inaccurate assuming that those using Angular rely on the default change detection. That alone produces so many countless bugs alone.
In the end, it really depends on the prior experience of the developer, as an MVC frequenter would probably like Angular better than React and a functional frequenter would prefer React.
Having come from Angular and moving into the React space, I have to say troubleshooting, preventing bugs, and optimizing has been sufficiently easier in React than in Angular.
Another positive case for React is the lack of the extra Module definitions. Why should you have to include a module to use a small piece of code from a library? There is just a lot of rigidity on Angular that will never be shaken off.
Some comments have been hidden by the post's author - find out more
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 would argue that 8 is not accurate since Angular provides cookie cutter training wheels to architect an application, whereas React gives you the flexibility to do significantly more good and bad with the right experience and skillset in mind.
I would also argue that 10 is slightly inaccurate assuming that those using Angular rely on the default change detection. That alone produces so many countless bugs alone.
In the end, it really depends on the prior experience of the developer, as an MVC frequenter would probably like Angular better than React and a functional frequenter would prefer React.
Having come from Angular and moving into the React space, I have to say troubleshooting, preventing bugs, and optimizing has been sufficiently easier in React than in Angular.
Another positive case for React is the lack of the extra Module definitions. Why should you have to include a module to use a small piece of code from a library? There is just a lot of rigidity on Angular that will never be shaken off.