I don’t think you have a very good understanding of how a browser works. You brought up “closer to metal” which is a term for servers that are not containerized or partitioned.
You are right about ecma standards sun setting some features of libraries and frameworks, which is what happened to ember with their ember object.
But that’s not comparable to react as react doesn’t provide features you’d ever want in a browser engine. State management and/or integration with state management. Build tool chains. DOM updating. These are all things that will never be a part of javascript as a language because they aren’t language problems. They are problems that happen when you start building complexity.
I don’t think you have a very good understanding of how a browser works. You brought up “closer to metal” which is a term for servers that are not containerized or partitioned.
You are right about ecma standards sun setting some features of libraries and frameworks, which is what happened to ember with their ember object.
But that’s not comparable to react as react doesn’t provide features you’d ever want in a browser engine. State management and/or integration with state management. Build tool chains. DOM updating. These are all things that will never be a part of javascript as a language because they aren’t language problems. They are problems that happen when you start building complexity.
This conversation is over from my side. Good day!
I think this statement is ridiculous.
Browsers manage their own state perfectly, in particular DOM updating. As far a build tools there are many other options unrelated to React.
Ok.