My view is that if the goal was to effectively make good software they wouldn’t start from scratch.

If they used wlroots the desktop would be usable today with a good feature set.

If they used Qt or GTK they would have feature rich well supported software. (GTK4 could have been an improvement for them, it’s designed around being minimal and having platform libraries implement design choices)

They didn’t take a practical approach imo. You could argue its a long term investment but because of it it’s probably years off of feature parity. The only upside today is… it’s written in Rust.

The project is motivated by “I like Rust, lets make a whole desktop in it” not by good UX.

Safari has supported mv2 extensions for years and recently added mv3 support.

However it never supported WebRequest blocking.

Brave claims they will maintain it in their fork but that won’t last long.

Developers don’t need to keep mv2 support, Firefox supports mv3 plus extra APIs on top.

I fixed it: https://github.com/flathub/com.valvesoftware.Steam/pull/1201

The bug is that they parse a glib keyfile with configparser which is a different format. So what is valid in one isn’t in the other.

More annoying because Mozilla does publish the stable flatpak, just not betas.

Flashback is based on old GNOME 2 code but unlike MATE it’s not maintained or improved.

deleted by creator

This is still a bug in the package, please report it.

The output and the renderer are separate and configurable concepts.

deleted by creator

deleted by creator

How the WebRequest API works is:

1. Network request is made
2. Sent to the WebExtension
3. Extension runs arbitrary JavaScript (Slow to very slow)
4. Repeat for every extension handling requests
5. Results eventually make it to the WebProcess where it belongs.

This is slow and will always be. Their change to remove blocking makes steps 2-4 a copy of the data instead of a synchronous call.

Now an ad can be slower, just by more data or bad JS. But that isn’t Googles concern because they sell those ads.

Correct, and the reasoning for removing blocking was performance.

deleted by creator

Are there numbers showing any meaningful harm to Sony or Nintendo?

If you are running things inside of containers you aren’t helping yourself by disabling unprivileged namespaces, you are actually just running more things as root. Inside the containers they generally block namespaces anyway.

TBH I’ve never heard anything positive about most of what hardened does.

deleted by creator

deleted by creator