<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><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><parent_chain></parent_chain></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>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>Vinnl</author><text>While I agree with the general gist of the article (and please, yes, it seems like a minor thing, but give us resizable iframes), except that &amp;quot;reactivity&amp;quot; does not meet the bar of developers collectively having landed on a solution to a common problem. There are a couple of frameworks with similar, but different, approaches to it, and yet none of them is truly widespread. I&amp;#x27;m very sceptical that standardisation would hit the right mark at this point in time.&lt;p&gt;But yes, that is basically what we saw with Web Components. People took drew the wrong conclusions about what problems React solved (&amp;quot;everything is a component&amp;quot;), and then tried to retrofit Web Components as a native solution to the problem - with the added assumption that just because it was built-in, it was better.</text><parent_chain></parent_chain></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>