<story><title>What We Need Instead of &quot;Web Components&quot;</title><url>https://blog.carlana.net/post/2023/web-component-alternative-futures/</url></story><parent_chain></parent_chain><comment><author>fevangelou</author><text>That&amp;#x27;s a great writeup.&lt;p&gt;As someone who&amp;#x27;s worked primarily on news&amp;#x2F;media sites for the last 15 years, I can totally relate and agree on all your points.&lt;p&gt;I would also argue that there are non-code issues that could easily be resolved. Bundling fonts for example. Decide on the top 100 with support for all or almost all characters, based on usage etc., and bundle them in the browser. That would shave possibly hundreds of KBs of each page&amp;#x27;s size.&lt;p&gt;On the flip side, stuff like lazy loading could become standard and use the attribute only to force-load content. Or stuff that is used on every freaking site (eg togglers as native html tags).&lt;p&gt;I&amp;#x27;m hopeful though.</text></comment>
<story><title>What We Need Instead of &quot;Web Components&quot;</title><url>https://blog.carlana.net/post/2023/web-component-alternative-futures/</url></story><parent_chain></parent_chain><comment><author>morrvs</author><text>Thanks for this, gives my intuition some words to back it up!&lt;p&gt;I find especially compelling how the author separates concrete problems like reconciliation (hard to argue against) from the abstract principle of &amp;quot;everything should be a component&amp;quot; (can be argued more easily IMO).&lt;p&gt;Shamelessly plugging &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;morris&amp;#x2F;vanilla-todo&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;morris&amp;#x2F;vanilla-todo&lt;/a&gt; here; in this try-hard-to-stay-vanilla case study there are similar conclusions: Reconciliation is hard, CSS global namespace is problematic, etc. - I also did not use web components, but could not explain&amp;#x2F;justify that decision well (until now!).</text></comment>