Your article perfectly sums up what I believe the goal of the Aurelia JavaScript framework is. To abide by emerging and pre-existing browser standards, not invent new ones or ways of writing code (I am looking at you React and your JSX).
All frameworks and libraries should share the same goal: to eventually be replaceable by native API'S. But, let's be honest. React and Vue are so far removed from real JavaScript and HTML, that will never happen.
Concepts like the Virtual DOM (a glorified dirty checker), sound cool from a marketing perspective but are not as performant as developers make them out to be.
Sadly, the Web Components specification seems to be a mess. I have hope one day it will turn out as well as ES6 did. Until native API's and specifications align more with the requirements of modern front-end development, we'll continue to see these abstractions and bastardisations of the language continue to be popular.
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.
Your article perfectly sums up what I believe the goal of the Aurelia JavaScript framework is. To abide by emerging and pre-existing browser standards, not invent new ones or ways of writing code (I am looking at you React and your JSX).
All frameworks and libraries should share the same goal: to eventually be replaceable by native API'S. But, let's be honest. React and Vue are so far removed from real JavaScript and HTML, that will never happen.
Concepts like the Virtual DOM (a glorified dirty checker), sound cool from a marketing perspective but are not as performant as developers make them out to be.
Sadly, the Web Components specification seems to be a mess. I have hope one day it will turn out as well as ES6 did. Until native API's and specifications align more with the requirements of modern front-end development, we'll continue to see these abstractions and bastardisations of the language continue to be popular.