After the whole debacle of manifest v3 they’re really choosing Chromium of all browsers to develop on?
Mozilla has made some controversial decisions but surely Firefox would be the better decision for the Linux and FOSS ecosystem.
Even better why not Librewolf?
Seeing this news makes me sad as there are better options available and the Linux foundation chose the worst one out of all of them.
Unfortunately, as much as I hate to admit it as someone who has left Chromium behind personally, Chromium is kind of the only choice. I think people outside the browser implementation world underestimate the sheer scale and complexity of the modern browser stack and what goes into maintaining compatibility with web standards, much less advancing them.
We’ve reached the point where Chromium is essentially the de-facto web standard because Chromium engineers do the lions’ share of feature testing and development, because Chromium receives the lions’ share of funding.
Igalia, an OSS consultancy that does a lot of fairly-funded independent browser development, has lots of material about this. For example, the recent chat between Igalia members and someone from Open Web Advocacy about what to do if the anitrust ruling against Google jeopardize’s Chromium’s funding, and the options are pretty dire.
Edit: After reading the article, I think this is a really good sign. Bringing together the immediate stakeholders in Chromium’s development and funding bodes well for the possibility of stewarding Chromium in a less Google-dependent, profit-motivated, ad-centric direction. There’s unfortunately a lot of uncertainty about how this will all shake out, but it’s possible that Chromium could become a truly independent project and move back in the direction of user value instead of user-hostile shareholder value.
With webassembly and webgl, why do browsers need to evolve? If you want some feature the browser doesn’t provide, just make it yourself and draw it onto the canvas. x86 assembly gets occasional performance improving instructions but fundamally it’s existed for 50 years and can continue to support all modern programs. X11 survived for 40 years before any talk of a replacement really appeared. Why can’t Chrome be maintenance only for 40 years and let apps and websites innovate on top of its primitives?
Chromium really?
After the whole debacle of manifest v3 they’re really choosing Chromium of all browsers to develop on?
Mozilla has made some controversial decisions but surely Firefox would be the better decision for the Linux and FOSS ecosystem.
Even better why not Librewolf?
Seeing this news makes me sad as there are better options available and the Linux foundation chose the worst one out of all of them.
Ironically I also just saw this here on the fediverse: Google loses in court, faces trial for collecting data on users who opted out
Or servo. Literally anything but chrome man.
@Static_Rocket@lemmy.world and @neblem@lemmy.world thanks for mentioning Servo👍
I didn’t know about that rust-based alternative until now and I agree; even Servo would’ve been a better choice than Chromium.
Linux Foundation is also the host for the Servo project.
Unfortunately, as much as I hate to admit it as someone who has left Chromium behind personally, Chromium is kind of the only choice. I think people outside the browser implementation world underestimate the sheer scale and complexity of the modern browser stack and what goes into maintaining compatibility with web standards, much less advancing them.
We’ve reached the point where Chromium is essentially the de-facto web standard because Chromium engineers do the lions’ share of feature testing and development, because Chromium receives the lions’ share of funding.
Igalia, an OSS consultancy that does a lot of fairly-funded independent browser development, has lots of material about this. For example, the recent chat between Igalia members and someone from Open Web Advocacy about what to do if the anitrust ruling against Google jeopardize’s Chromium’s funding, and the options are pretty dire.
Edit: After reading the article, I think this is a really good sign. Bringing together the immediate stakeholders in Chromium’s development and funding bodes well for the possibility of stewarding Chromium in a less Google-dependent, profit-motivated, ad-centric direction. There’s unfortunately a lot of uncertainty about how this will all shake out, but it’s possible that Chromium could become a truly independent project and move back in the direction of user value instead of user-hostile shareholder value.
With webassembly and webgl, why do browsers need to evolve? If you want some feature the browser doesn’t provide, just make it yourself and draw it onto the canvas. x86 assembly gets occasional performance improving instructions but fundamally it’s existed for 50 years and can continue to support all modern programs. X11 survived for 40 years before any talk of a replacement really appeared. Why can’t Chrome be maintenance only for 40 years and let apps and websites innovate on top of its primitives?