<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>grincho</author><text>&amp;gt; It isn&amp;#x27;t enough to explain how fast Firefox feels now.&lt;p&gt;That&amp;#x27;s because we&amp;#x27;ve been making a dedicated effort to find and stamp out sources of UI lag! It&amp;#x27;s called Quantum Flow; see &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wiki.mozilla.org&amp;#x2F;Quantum&amp;#x2F;Flow&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wiki.mozilla.org&amp;#x2F;Quantum&amp;#x2F;Flow&lt;/a&gt; for more.</text><parent_chain><item><author>DiabloD3</author><text>As someone that jumped ship from how slow Chrome has gotten and went to Nightly &amp;#x2F;w Stylo and (CPU threads - 1) e10s processes enabled about 2 monthsish ago...&lt;p&gt;Holy damn Firefox is actually fast.&lt;p&gt;Fair comparison, both having Pocket, uBlock, Evernote, OneNote, Pushbullet, and Bitwarden; neither of them having an extension the other doesn&amp;#x27;t. Above described Firefox Nightly config vs Chrome Dev.&lt;p&gt;Test machines are a workstation with a i7-4771 @ 3.9ghz, 32GB DDR3-2133, Radeon 7970 with a trio of 1080p screens (a very fast modern machine from the Haswell era) and a laptop with a i5-32120M, 8GB of DDR3-1600, Intel HD4000 iGPU feeding a 13&amp;quot; 2560x1600 @ 200% hidpi (an Ivy Bridge era MBPr 13&amp;quot; Late 2012). Both machines run Win10.&lt;p&gt;Both machines have less real world wait on Firefox than Chrome, and the interface has less latency between when I do something and it even begins processing the request. Also, under a ton of windows and tabs, Firefox seems to use less RAM and the speed gap seems to widen.&lt;p&gt;I don&amp;#x27;t care about about artificial benchmarks, btw, they never seem to measure what actually makes browsers slower for humans.&lt;p&gt;Edit: Even though I just said I don&amp;#x27;t care about benchmarks, using Speedometer 2.0-r2216: On the workstation: Firefox 58.0a1 2017-09-26 64bit 61.18 vs Chrome 63.0.3217.0 dev 64-bit 51.67; on the laptop, same versions: Firefox 28.58 vs Chrome 26.74&lt;p&gt;So, arguably, flat out benchmarkable performance is the same, with Firefox just slightly edging ahead (18% and 6% faster). It isn&amp;#x27;t enough to explain how fast Firefox feels now.&lt;p&gt;Edit 2: And now with Edge 40.15063.0.0&amp;#x2F;EdgeHTML 15.15063: Workstation, 46.72; Laptop 21.37. Firefox is 34% and 31% faster, Chrome is 25% and 11% faster.</text></item></parent_chain></comment><story><title>Firefox Quantum Lands in Beta, Developer Edition</title><url>https://blog.mozilla.org/blog/2017/09/26/firefox-quantum-beta-developer-edition/</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>low_battery</author><text>Unfortunately, as long as Firefox security infrastructure does not match Chrome, I can not use it. Note that errors like use-after-free and buffer overflows are marked as Critical (run arbitrary code on computer) for Firefox, but marked as High (execute code in the context of, or otherwise impersonate other origins.) for Chrome because of sandboxing.&lt;p&gt;Firefox: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.mozilla.org&amp;#x2F;en-US&amp;#x2F;security&amp;#x2F;known-vulnerabilities&amp;#x2F;firefox&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.mozilla.org&amp;#x2F;en-US&amp;#x2F;security&amp;#x2F;known-vulnerabilities...&lt;/a&gt;&lt;p&gt;Chrome: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;chromereleases.googleblog.com&amp;#x2F;search&amp;#x2F;label&amp;#x2F;Stable%20updates&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;chromereleases.googleblog.com&amp;#x2F;search&amp;#x2F;label&amp;#x2F;Stable%20...&lt;/a&gt;&lt;p&gt;Hopefully with their sandboxing project done (Also with Rust) will make Firefox much better in the security department, but until then, no.</text><parent_chain><item><author>DiabloD3</author><text>As someone that jumped ship from how slow Chrome has gotten and went to Nightly &amp;#x2F;w Stylo and (CPU threads - 1) e10s processes enabled about 2 monthsish ago...&lt;p&gt;Holy damn Firefox is actually fast.&lt;p&gt;Fair comparison, both having Pocket, uBlock, Evernote, OneNote, Pushbullet, and Bitwarden; neither of them having an extension the other doesn&amp;#x27;t. Above described Firefox Nightly config vs Chrome Dev.&lt;p&gt;Test machines are a workstation with a i7-4771 @ 3.9ghz, 32GB DDR3-2133, Radeon 7970 with a trio of 1080p screens (a very fast modern machine from the Haswell era) and a laptop with a i5-32120M, 8GB of DDR3-1600, Intel HD4000 iGPU feeding a 13&amp;quot; 2560x1600 @ 200% hidpi (an Ivy Bridge era MBPr 13&amp;quot; Late 2012). Both machines run Win10.&lt;p&gt;Both machines have less real world wait on Firefox than Chrome, and the interface has less latency between when I do something and it even begins processing the request. Also, under a ton of windows and tabs, Firefox seems to use less RAM and the speed gap seems to widen.&lt;p&gt;I don&amp;#x27;t care about about artificial benchmarks, btw, they never seem to measure what actually makes browsers slower for humans.&lt;p&gt;Edit: Even though I just said I don&amp;#x27;t care about benchmarks, using Speedometer 2.0-r2216: On the workstation: Firefox 58.0a1 2017-09-26 64bit 61.18 vs Chrome 63.0.3217.0 dev 64-bit 51.67; on the laptop, same versions: Firefox 28.58 vs Chrome 26.74&lt;p&gt;So, arguably, flat out benchmarkable performance is the same, with Firefox just slightly edging ahead (18% and 6% faster). It isn&amp;#x27;t enough to explain how fast Firefox feels now.&lt;p&gt;Edit 2: And now with Edge 40.15063.0.0&amp;#x2F;EdgeHTML 15.15063: Workstation, 46.72; Laptop 21.37. Firefox is 34% and 31% faster, Chrome is 25% and 11% faster.</text></item></parent_chain></comment><story><title>Firefox Quantum Lands in Beta, Developer Edition</title><url>https://blog.mozilla.org/blog/2017/09/26/firefox-quantum-beta-developer-edition/</url></story>