<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>evmar</author><text>&amp;gt; seems to compare the Firefox version number with 65 ... I’ve no idea what the purpose of this is&lt;p&gt;I previously worked on JS infra at Google.  Google uses a lot of shared JS libraries that date back over a decade, and those libraries have accumulated lots of workarounds for browsers that nobody cares about anymore.  (One especially crazy seeming one from today&amp;#x27;s perspective is that there&amp;#x27;s a separate implementation of event propagation, I believe because because it dates back to browsers that only implemented one half of event bubbling&amp;#x2F;capture!)&lt;p&gt;It&amp;#x27;s very difficult to remove an old workaround because&lt;p&gt;1. it&amp;#x27;s hard to be completely sure nobody actually depends on the workaround (especially given the wide variety of apps and environments Google supports -- Firefox aside, Google JS runs on a lot of abandonware TVs), and&lt;p&gt;2. it&amp;#x27;s hard to prioritize doing such work, because it&amp;#x27;s low value (a few less bytes of JS) and nonzero risk (see point 1) without meaningfully moving any metrics you care about.&lt;p&gt;In all, how to eliminate accumulated cruft like is a fascinating problem to me in that I can&amp;#x27;t see how it ever gets done.  And it&amp;#x27;s not a Google thing.  Even the newer cooler startup I now work at has similar &amp;quot;work around old Safari bug, not sure if it&amp;#x27;s safe to remove&amp;quot; codepaths that I can imagine will stick around forever, for similar reasons.</text><parent_chain></parent_chain></comment><story><title>Google Docs in a clean-room browser</title><url>https://www.ekioh.com/devblog/google-docs-in-a-clean-room-browser/</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>devwastaken</author><text>*Closed source browser.&lt;p&gt;Flow is yet another project pulling on open source resources, and the browser market created from open browsers, and trying to privatize it. Imagine if google could just make whatever internal changes to chromium and nobody knew about it.</text><parent_chain></parent_chain></comment><story><title>Google Docs in a clean-room browser</title><url>https://www.ekioh.com/devblog/google-docs-in-a-clean-room-browser/</url></story>