<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>blibble</author><text>I was fully in the Google world prior to gorhill&amp;#x27;s posts on manifest v3&lt;p&gt;as a direct result the only thing I have left is a pixel phone, which will be going with the new iPhone&lt;p&gt;(and in the meantime my entire family has been &amp;#x27;helpfully&amp;#x27; migrated too)&lt;p&gt;I may be up the extreme end of the distribution, but this sort of grassroots push is what dethroned IE, and the resultant loss of control of the web eliminated Microsoft&amp;#x27;s near total influence over the computing industry</text><parent_chain><item><author>horsawlarway</author><text>I approve (of both the release and the name).&lt;p&gt;I see plenty of folks in here lamenting this release at all - in the hopes that the lack of it will push folks to Firefox.  It won&amp;#x27;t.  Those who care about this are already on Firefox, and frankly - Firefox isn&amp;#x27;t going to be the answer here (to be clear, this is opinion).&lt;p&gt;I&amp;#x27;m also not thrilled at manifest v3, although for very different reasons than the adblocking limitations - I do lots of extension development, and I think the service worker approach taken is a &lt;i&gt;bad&lt;/i&gt; mistake, forcing a distributed consensus model onto extensions without understanding the limitations that model imposes given how often extensions span multiple js contexts (across tabs&amp;#x2F;frames&amp;#x2F;content_scripts&amp;#x2F;windows&amp;#x2F;etc).&lt;p&gt;Frankly - the environment is also still riddled with bugs... everything from docs that are wrong, to &lt;i&gt;serious&lt;/i&gt; issues like a service worker not activating on simple, basic, required events (like chrome.action.onClicked, which is literally about as basic as it gets for extensions).&lt;p&gt;Overall - my first impression of the manifest v3 upgrade was fairly neutral (it&amp;#x27;s not really solving any of my pain points, and it requires a lot of changes to support - but it seemed functional).  My opinion after porting several large extension projects to the space is... bad.  It&amp;#x27;s a bad set of changes as implemented in chromium right now.</text></item></parent_chain></comment><story><title>“UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3</title><url>https://github.com/gorhill/uBlock/commit/a559f5f2715c58fea4de09330cf3d06194ccc897</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>rjh29</author><text>&amp;gt; I see plenty of folks in here lamenting this release at all - in the hopes that the lack of it will push folks to Firefox. It won&amp;#x27;t. Those who care about this are already on Firefox&lt;p&gt;Huh? I&amp;#x27;m going to switch to Firefox the second uBlock Origin stops working on Chrome. Otherwise I&amp;#x27;ll continue to use Chrome because it&amp;#x27;s a better browser (for me). I don&amp;#x27;t think I&amp;#x27;m some rare minority here.</text><parent_chain><item><author>horsawlarway</author><text>I approve (of both the release and the name).&lt;p&gt;I see plenty of folks in here lamenting this release at all - in the hopes that the lack of it will push folks to Firefox.  It won&amp;#x27;t.  Those who care about this are already on Firefox, and frankly - Firefox isn&amp;#x27;t going to be the answer here (to be clear, this is opinion).&lt;p&gt;I&amp;#x27;m also not thrilled at manifest v3, although for very different reasons than the adblocking limitations - I do lots of extension development, and I think the service worker approach taken is a &lt;i&gt;bad&lt;/i&gt; mistake, forcing a distributed consensus model onto extensions without understanding the limitations that model imposes given how often extensions span multiple js contexts (across tabs&amp;#x2F;frames&amp;#x2F;content_scripts&amp;#x2F;windows&amp;#x2F;etc).&lt;p&gt;Frankly - the environment is also still riddled with bugs... everything from docs that are wrong, to &lt;i&gt;serious&lt;/i&gt; issues like a service worker not activating on simple, basic, required events (like chrome.action.onClicked, which is literally about as basic as it gets for extensions).&lt;p&gt;Overall - my first impression of the manifest v3 upgrade was fairly neutral (it&amp;#x27;s not really solving any of my pain points, and it requires a lot of changes to support - but it seemed functional).  My opinion after porting several large extension projects to the space is... bad.  It&amp;#x27;s a bad set of changes as implemented in chromium right now.</text></item></parent_chain></comment><story><title>“UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3</title><url>https://github.com/gorhill/uBlock/commit/a559f5f2715c58fea4de09330cf3d06194ccc897</url></story>