I think a lot of this is addressing problems that aren't really relevant anymore. Yes, it'd be nice if we could all come together and hold hands and agree on better standards for fundamental parts of front-end...but there's never going to be full agreement on what those standards are. And that's fine!
The modern front-end landscape benefits tremendously from the plethora of options available. It's not a one-size-fits-all world. Some developers may click with the "we are building serious apps here" approach of Angular, some maybe like the flexibility-with-first-party-support of Vue, and some people like me love how React gives you a start and says "go figure the rest out." And that's just the three big ones.
If you or your team is having issues choosing with the technology stack, and feeling overwhelmed, that's certainly valid - but it's also a fundamental part of software development, not something new or unique to front-end. Having all of these choices means having to need to be familiar with the pros and cons of each, and making an informed decision from there - this is an excellent skill to have as a developer. A necessary one, even. Note that this does not mean you have to be an expert in 50 different frameworks, that's a strawman that isn't remotely realistic.
Framework churn hasn't really been a thing for...years, now? Which is eternity in web dev time. The only notable framework that I've seen people thinking about jumping ship to is Svelte, and that's because it 1) does the technical bits differently and 2) offers a brilliant API. Long gone are the days of "ha ha JavaScript has a new framework every week."
This isn't even touching on how the browser itself is a problematic platform...because Google, and Apple on iOS, basically dictates everything. See Edge moving to Chromium. Until that elephant is addressed, the room isn't remotely equipped to deal with implementing agreed-upon standards that can be "free" of inordinate influence from one particular company.
All said - this is a great perspective on the importance of standards in general. We of course need them, and as mentioned we have some amazing ones via WC3, WCAG, and TC39. But I just don't think web components, as they exist today, are the solution, nor is the current framework landscape really much of a problem.
Standards come from standards bodies and are actual when implemented to a certain extent by multiple engine vendors... There's not much ambiguity in what the standards are. Try again.
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 think a lot of this is addressing problems that aren't really relevant anymore. Yes, it'd be nice if we could all come together and hold hands and agree on better standards for fundamental parts of front-end...but there's never going to be full agreement on what those standards are. And that's fine!
The modern front-end landscape benefits tremendously from the plethora of options available. It's not a one-size-fits-all world. Some developers may click with the "we are building serious apps here" approach of Angular, some maybe like the flexibility-with-first-party-support of Vue, and some people like me love how React gives you a start and says "go figure the rest out." And that's just the three big ones.
If you or your team is having issues choosing with the technology stack, and feeling overwhelmed, that's certainly valid - but it's also a fundamental part of software development, not something new or unique to front-end. Having all of these choices means having to need to be familiar with the pros and cons of each, and making an informed decision from there - this is an excellent skill to have as a developer. A necessary one, even. Note that this does not mean you have to be an expert in 50 different frameworks, that's a strawman that isn't remotely realistic.
Framework churn hasn't really been a thing for...years, now? Which is eternity in web dev time. The only notable framework that I've seen people thinking about jumping ship to is Svelte, and that's because it 1) does the technical bits differently and 2) offers a brilliant API. Long gone are the days of "ha ha JavaScript has a new framework every week."
This isn't even touching on how the browser itself is a problematic platform...because Google, and Apple on iOS, basically dictates everything. See Edge moving to Chromium. Until that elephant is addressed, the room isn't remotely equipped to deal with implementing agreed-upon standards that can be "free" of inordinate influence from one particular company.
All said - this is a great perspective on the importance of standards in general. We of course need them, and as mentioned we have some amazing ones via WC3, WCAG, and TC39. But I just don't think web components, as they exist today, are the solution, nor is the current framework landscape really much of a problem.
Standards come from standards bodies and are actual when implemented to a certain extent by multiple engine vendors... There's not much ambiguity in what the standards are. Try again.