104

A list of recent hostile moves by #Google's #Chrome team (Jeff Fortin T. (@nekohayo@mastodon.social)) (mastodon.social)

submitted 11 months ago* (last edited 11 months ago) by fsniper@kbin.social to c/technology@beehaw.org

27 comments fedilink hide all child comments

A 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/

you are viewing a single comment's thread
view the rest of the comments

[-] comicallycluttered@beehaw.org 3 points 11 months ago* (last edited 11 months ago)

We did have people developing a new browser engine. It was called Servo and Mozilla went and killed the project.

Maybe it just wasn't going anywhere and they didn't think it was right for Firefox, maybe it was experiment for experiment's sake, maybe it was always destined to be a side project. I don't know.

It's still being developed, but doesn't have nearly as much manpower and funding as it did at Mozilla.

Honestly, my very uninformed opinion is that there should be more browsers developed using WebKit.

It's still FOSS (despite Apple's best efforts) and it's widely supported due to Safari's market share (particularly on mobile).

I'm just not familiar with how easy it is to implement outside of Apple (I know GNOME Web uses a GTK port), or how well current popular extensions can integrate with it.

Then again, I assume we'd be having the same argument, except complaining that it's Apple, rather than Google, that has too much control over the web.

[-] OneRedFox@beehaw.org 5 points 11 months ago

We did have people developing a new browser engine. It was called Servo and Mozilla went and killed the project.

Maybe it just wasn’t going anywhere and they didn’t think it was right for Firefox, maybe it was experiment for experiment’s sake, maybe it was always destined to be a side project. I don’t know.

Servo was an experimental browser engine for Mozilla that they were using as a testing ground for their investment into the Rust programming language; the project did bear fruit as components were slowly integrated into Firefox starting at version 57 with Project Quantum. They did eventually complete that transition and everyone using an up-to-date version of Firefox is using various Servo components (I'm personally a big fan). Unfortunately, when COVID devastated the economy Mozilla axed some of their side projects, which included Servo itself. Maybe we'll see further investment in the future, but they did already do what they wanted to with it for the most part.