Use web components for what they’re good at
I appreciate the author&#x27;s attempt to contextualize web components, but I have a few bones to pick, having seen web components used to a pathological extent in various projects<p>First, the idea that one of web components&#x27; strengths is bypassing serverside rendering is a bit misleading.  SSR has been foundational to reducing time to first meaningful paint, ensuring accessibility, and improving seo. to argue that bypassing it is an advantage seems antithetical to best practices, even when using client-side tech like web components.<p>Second, the transition example from react to svelte highlights the use of web components as a bridge, but I fear it oversimplifies the reality of such transitions. Its true that web components might provide a superficial level of interoperability, underneath, the application architecture, state management, and data flow can differ vastly between frameworks. Simply plopping an old component with a new one doesn’t mean they’ll play nice without substantial architectural considerations.<p>Finally, the mention of &quot;no bundler, no transpiler&quot; as an advantage is curious. in practice, the modern web development ecosystem has moved towards using tools like bundlers and transpilers to optimize delivery, reduce overhead, and facilitate modular development. this isn&#x27;t about complexity, but rather about efficiency and best practices.<p>Web components certainly have their place and, used judiciously, can certainly add value. It&#x27;s just essential to approach them with a nuanced understanding and not as a silver bullet.