Mozilla on the coming version-100 apocalypse

Posted Feb 17, 2022 10:08 UTC (Thu) by cthart (guest, #4457)
In reply to: Mozilla on the coming version-100 apocalypse by pabs
Parent article: Mozilla on the coming version-100 apocalypse

I'm with pabs here. Just bump the verison to 100 and let the fallout happen. We need to have more changes like this happen more regularly for folk to realise that they can't just make assumptions, and to learn from our past mistakes. We have a whole generation of programmers now that didn't have to deal with Y2K and they also need to learn its lessons.

to post comments

Mozilla on the coming version-100 apocalypse

Posted Feb 17, 2022 12:29 UTC (Thu) by mgedmin (guest, #34497) [Link] (4 responses)

Will websites care? "Firefox can't render our site? Just use Chrome."

Will users care? "Site works in Chrome, doesn't work in Firefox? I'll just use Chrome then! Firefox must be a bad browser."

Mozilla on the coming version-100 apocalypse

Posted Feb 17, 2022 12:30 UTC (Thu) by pabs (subscriber, #43278) [Link] (3 responses)

The post says that Chrome is coming up on version 100 too, and has also enabled the same option as Firefox.

Mozilla on the coming version-100 apocalypse

Posted Feb 17, 2022 23:39 UTC (Thu) by khim (subscriber, #9252) [Link] (2 responses)

Then people would just take Chromium (or Firefox) sources and release version which “works”.

Remember how that happened with Flash last year?

With Flash that was a stop-gap solution because Flash required so many hacks in different parts of browser that it wasn't really practical to forward-port the change.

When you only need to change UA string… that “extra-compatible” browser can be supported for a very long time.

Mozilla on the coming version-100 apocalypse

Posted Feb 18, 2022 10:20 UTC (Fri) by rqosa (subscriber, #24136) [Link] (1 responses)

> When you only need to change UA string…

Aren't there simpler ways to accomplish that than recompiling the browser from source (which, if used by end-users outside of an intranet managed by an IT department, would presumably also require the end-users to download & install the resulting "alternate version" of the browser)? Such as: using Firefox's "general.useragent.override" setting in about:config, or using a Chrome extension or a Firefox add-on.

Mozilla on the coming version-100 apocalypse

Posted Feb 18, 2022 13:59 UTC (Fri) by geert (subscriber, #98403) [Link]

No need to recompile from source, a hex editor is all you need to change the User-Agent string.