<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>eps</author><text>This will probably get downvoted quickly, but Chrome&apos;s updater is one of few things I quarantine on my machine. I just don&apos;t trust Google enough to let it run stuff that &quot;works quietly in the background, never notifying you.&quot; The technology is interesting (though not exactly a rocket science and certainly not &lt;i&gt;magical&lt;/i&gt; ... which it would&apos;ve been if it could update a running instance of Chrome without restarting it), but I am wee bit uncomfortable letting a company who is in business of collecting data and tracking people to run anything in my background.</text><parent_chain></parent_chain></comment><story><title>Chrome&apos;s Most Important Feature </title><url>http://googlesystem.blogspot.com/2011/08/chromes-most-important-feature.html</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>DanielBMarkham</author><text>I agree with this. Chrome has effectively changed the entire nature of client-side computing with this feature. If you want to run stuff client-side any more (hello Windows? Anybody listening?), you&apos;re going to need to implement this.&lt;p&gt;In general, the user should &lt;i&gt;extremely&lt;/i&gt; rarely be interrupted for anything, especially not anything program-related. Each program having a tray icon, an update alert, update restarts, and flow interruption because it thinks something is important is what has turned windows from a productive computing platform to some kind of cross between a Kafkaesque X-box and a slot machine.</text><parent_chain></parent_chain></comment><story><title>Chrome&apos;s Most Important Feature </title><url>http://googlesystem.blogspot.com/2011/08/chromes-most-important-feature.html</url></story>