<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>rst</author><text>There is no single TCP monoculture codebase -- even among Unix-alikes, the Linux networking stack is a reimplementation, with no common ancestry with the BSD stack. (To say nothing of routers with their own implementations, often including hardware assist at the high end.)</text><parent_chain><item><author>MR4D</author><text>Why does nobody say “the TCP&amp;#x2F;IP monoculture is maddening,” or “the HTML monoculture is maddening” ?&lt;p&gt;Seriously, I need somebody to explain it to me because I don’t get it.&lt;p&gt;Having one core base of code is not a bad thing to me.&lt;p&gt;What am I missing here?</text></item><item><author>leeoniya</author><text>the webkit monoculture is saddening.&lt;p&gt;just yesterday i ran into chrome&amp;#x27;s 2016 img&amp;#x2F;flex-basis bug which works properly in firefox but requires an extra wrapping div as a work-around in chrome.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;chromium&amp;#x2F;issues&amp;#x2F;detail?id=625560&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;chromium&amp;#x2F;issues&amp;#x2F;detail?id=625560&lt;/a&gt;&lt;p&gt;what possible motivation is there to fix it when you&amp;#x27;re not competing with anyone?&lt;p&gt;hopefully microsoft can help fix it now?&lt;p&gt;also yesterday, i was writing some ui tests that use getBoundingClientRect() at different media query breakpoints. not only does chrome intermittently fail to deliver consistent results between runs (even with judicious timeouts), at different screen pixel densities its rounding errors are &lt;i&gt;several&lt;/i&gt; pixels off and accumulate to bork all tests in a major way. on the other hand, firefox behaves deterministically across test runs and there&amp;#x27;s a &lt;i&gt;single&lt;/i&gt; pixel (non-accumulating) error in one of several hundred tests.&lt;p&gt;somehow, i made it through the dark ages of IE6 without permanent hair loss, but i dont have fond memories of those years in my career.&lt;p&gt;now manifest v3 is starting to roll out in Chrome 80. once uBlock Origin stops working, i will use chrome even less (i try only to use it for its devtools currently)</text></item></parent_chain></comment><story><title>The Era of the Trident Engine</title><url>https://schepp.dev/posts/today-the-trident-era-ends/</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>Uehreka</author><text>TCP&amp;#x2F;IP is a protocol and HTML is a format. The reason that’s OK is that lots of people have built different TCP&amp;#x2F;IP stacks and HTML renderers, and so no one person&amp;#x2F;organization can control them. They aren’t “one codebase”.</text><parent_chain><item><author>MR4D</author><text>Why does nobody say “the TCP&amp;#x2F;IP monoculture is maddening,” or “the HTML monoculture is maddening” ?&lt;p&gt;Seriously, I need somebody to explain it to me because I don’t get it.&lt;p&gt;Having one core base of code is not a bad thing to me.&lt;p&gt;What am I missing here?</text></item><item><author>leeoniya</author><text>the webkit monoculture is saddening.&lt;p&gt;just yesterday i ran into chrome&amp;#x27;s 2016 img&amp;#x2F;flex-basis bug which works properly in firefox but requires an extra wrapping div as a work-around in chrome.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;chromium&amp;#x2F;issues&amp;#x2F;detail?id=625560&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;chromium&amp;#x2F;issues&amp;#x2F;detail?id=625560&lt;/a&gt;&lt;p&gt;what possible motivation is there to fix it when you&amp;#x27;re not competing with anyone?&lt;p&gt;hopefully microsoft can help fix it now?&lt;p&gt;also yesterday, i was writing some ui tests that use getBoundingClientRect() at different media query breakpoints. not only does chrome intermittently fail to deliver consistent results between runs (even with judicious timeouts), at different screen pixel densities its rounding errors are &lt;i&gt;several&lt;/i&gt; pixels off and accumulate to bork all tests in a major way. on the other hand, firefox behaves deterministically across test runs and there&amp;#x27;s a &lt;i&gt;single&lt;/i&gt; pixel (non-accumulating) error in one of several hundred tests.&lt;p&gt;somehow, i made it through the dark ages of IE6 without permanent hair loss, but i dont have fond memories of those years in my career.&lt;p&gt;now manifest v3 is starting to roll out in Chrome 80. once uBlock Origin stops working, i will use chrome even less (i try only to use it for its devtools currently)</text></item></parent_chain></comment><story><title>The Era of the Trident Engine</title><url>https://schepp.dev/posts/today-the-trident-era-ends/</url></story>