Have to disagree. JavaScript and React do work well together, embracing the prototype-based, modular composition, Dan Abramov school of OOP. But angular seems to want to abstract all that in favor of the classical inheritance hierarchy Martin Fowler school of OOP.
A JS expert would probably scoff at how restrictive angular feels. Given something like a Salesforce api metadata-generated data model would be easier to work with in a prototype system vs class model.
But I'm biased. I don't think modern application infrastructure warrants classical OOP patterns, which were designed for large code bases.
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.
Have to disagree. JavaScript and React do work well together, embracing the prototype-based, modular composition, Dan Abramov school of OOP. But angular seems to want to abstract all that in favor of the classical inheritance hierarchy Martin Fowler school of OOP.
A JS expert would probably scoff at how restrictive angular feels. Given something like a Salesforce api metadata-generated data model would be easier to work with in a prototype system vs class model.
But I'm biased. I don't think modern application infrastructure warrants classical OOP patterns, which were designed for large code bases.