Yes React is technically a library. That's great. But it almost always encompasses the entire application, tightly coupling with every part of the codebase, forcing you to write your code in a way that adheres to React's rules. It might as well be a framework.
And even if React is a library and not a framework, all of the points made here still apply so why is it necessary to point this out?
Agreed! Thanks for bring that out, Jack! My intention it is to help beginners in development to understand the role of frameworks at very entry level, and not confuse them about semantics.
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.
This is such a tired argument about semantics.
Yes React is technically a library. That's great. But it almost always encompasses the entire application, tightly coupling with every part of the codebase, forcing you to write your code in a way that adheres to React's rules. It might as well be a framework.
And even if React is a library and not a framework, all of the points made here still apply so why is it necessary to point this out?
Agreed! Thanks for bring that out, Jack! My intention it is to help beginners in development to understand the role of frameworks at very entry level, and not confuse them about semantics.