3 ms·
> paid by Google to specify Web Components between 2008 and 2021 - a technology in direct competition with React at the time I’m personally of the belief that
by afavour 3y ago
> paid by Google to specify Web Components between 2008 and 2021 - a technology in direct competition with React at the time
I’m personally of the belief that we should assess arguments, not employer. Someone working on a competitor to React can make very valid arguments against it, they’re often some of the most knowledgeable people about the drawbacks of the framework.
I’m personally not a fan of Alex’s abrasive style but I’ve seen plenty of his critiques of sites written in React-based stacks and they’re usually evidenced with bundle analysis, burn down charts and so on. They’re not unfounded.
(I also disagree that Web Components are a competitor to React. Frameworks like Preact and Svelte are interoperable with Web Components and build on top of the API. React chooses not to but that’s neither here nor there)
- flakiness 3y ago> (I also disagree that Web Components are a competitor to React. Frameworks like Preact and Svelte are interoperable with Web Components and build on top of the API. React chooses not to but that’s neither here nor there) Used to work on Web Components (the browser side.) Although we didn't take it as a competitor, in hindsight it was - at least in a sense. Both are component-based technologies, and the expressiveness of React and ES6+ made WC less relevant. I think WC is still nice to have, but it is no longer a must-have as it was originally envisioned. The JS ecosystem has largely solved the problem by themselves without browser vendor's help (besides improvements of JS itself.)
- jitl 3y agoNeither Preact or Svelte produce web components by default or use features like Shadow DOM.
- afavour 3y agoI’m not sure how that’s relevant to the point that Web Components is an API that can coexist with frontend frameworks.