I have a bit of a contrary view on a few of the items, not that I am defending web components, I have my own issues about them but my point is to offer a differ

I have a bit of a contrary view on a few of the items, not that I am defending web components, I have my own issues about them but my point is to offer a different perspective on a few of these items: 1. Progressive enhancement - but I think that websites should work without JavaScript wherever possible At a certain point, backwards compatibility becomes more a of hindrance than a help, in an effort to support an ever shrinking demographic. Now I will give the author the fact that they used the word website, where my frame of reference is building modern web applications, falling back to no-javascript to me would be going back to server rendering and the dumpster-fire of page-post AS/JS/PH/P's. 2. CSS in, err... JS Separation of technology, is not separation of concerns. This has been argued over JSX and it has been shown to be a huge productivity improvement. If everything for a component is internal to that component and does not need to be reused in a way other than using that component then there is no reason to separate the technology. As both of their concerns are the UI component. In that regard, where everything is encapsulated to the component (HTML, CSS, JS) it is actually a better pattern to not separate technologies as it makes the component easier to reason about.