where ‘absolutely not’ means ‘maybe later’
https://www.youtube.com/watch?v=c40irxnC_qM&list=UU9rJrMVgcXTfa8xuMnbhAEA - video
https://pivottoai.libsyn.com/20251223-firefox-browser-falls-to-ai-what-do-we-do-now - podcast
time: 9 min 39 sec
where ‘absolutely not’ means ‘maybe later’
https://www.youtube.com/watch?v=c40irxnC_qM&list=UU9rJrMVgcXTfa8xuMnbhAEA - video
https://pivottoai.libsyn.com/20251223-firefox-browser-falls-to-ai-what-do-we-do-now - podcast
time: 9 min 39 sec
Presumably, if Firefox version N breaks ad-blocking, someone can make a hard fork of version N-1. Security patches, upgrades to OS support and things like new CSS/HTML features can be cherry-picked or reimplemented to it, though Firefox updates in general will not be admitted, as it’s a hard fork (in the way that LibreOffice or MariaDB is). At worst, Firefox will actively make it hard to do this, closing their source or changing their licence to one which prohibits it, requiring any updates to be reimplemented clean-room style, which will slow things down, though if the alternative is actively enshittified, it’s the least-bad option.
The good news is it generally isn’t necessary to reverse engineer browser behavior when writing a browser. Since it’s mostly fairly standardized, there’s a decent test suite, and the major browsers are all open source.
Though this comes with some caveats: