329
Jeff Fortin T. (@nekohayo@mastodon.social)
mastodon.socialA list of recent hostile moves by #Google's #Chrome team; handy for sharing with your entourage, to explain why they should stop using #Chromium / #GoogleChrome and use #Firefox or #Epiphany as their main #web #browser :
* The "Manifest v3" sabotage of content blocking extensions: https://www.theverge.com/2022/6/10/23131029/mozilla-ad-blocking-firefox-google-chrome-privacy-manifest-v3-web-request
* The attempted sabotage of #JPEGXL: https://www.cnet.com/tech/computing/chrome-banishes-jpeg-xl-photo-format-that-could-save-phone-space/
* #WebEnvironmentIntegrity a.k.a. #DRM for whole websites would hurt the web, #opensource browsers and OSes: https://arstechnica.com/gadgets/2023/07/googles-web-integrity-api-sounds-like-drm-for-the-web/
It really didn’t… Firefox has been neck and neck performance wise the entire time with a massive arsenal of extensions (and to be fair some of those extensions did negatively impact performance enough to scare people off) and I can’t think of a major feature Firefox didn’t have first or get soon after.
Chrome largely just became a “speed meme” though among enthusiasts and had the backing from Google to win over IT teams.