<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>oliwarner</author><text>Interesting. I use full Vue for this  quite a lot, mount onto specific DOM points, replace their content with (most commonly) an enhanced form, or a data table. Works well, costs 30Kb plus compat layers. You can argue all day long about the cost of 30Kb, but then you put a 200Kb image in your header.&lt;p&gt;Anyway, looking at the docs, my approach wouldn&amp;#x27;t be as easy in vue-petite. It looks like Components have been functionally gutted. You can still approximate something, but you seem to lose a lot of ecosystem benefits of Vue. Theirs looks great for&lt;p&gt;Ultimately, this all seems like something coverage and tree-shaking &lt;i&gt;should&lt;/i&gt; be able to do. If you&amp;#x27;re only using 5Kb of Vue, only 5Kb should be bundled. One day, eh? Until then, is the additional 25Kb actually hurting your users?</text><parent_chain></parent_chain></comment><story><title>Petite-Vue – 5kb subset of Vue optimized for progressive enhancement</title><url>https://github.com/vuejs/petite-vue</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>manigandham</author><text>This progressive enhancement is exactly why I prefer Vue and find it so productive. 95% of apps are best built as server-side rendered with reactivity on top of each page as needed (instead of the JS&amp;#x2F;SPA monstrosities we have today).&lt;p&gt;Nice to see an even lighter version optimized for this use-case.</text><parent_chain></parent_chain></comment><story><title>Petite-Vue – 5kb subset of Vue optimized for progressive enhancement</title><url>https://github.com/vuejs/petite-vue</url></story>