

If it’s a solid extension which could be used by other websites, and it’s explained clearly like in your post by the website which needs it, then probably yes.
You die twice. One time when you stop breathing, and a second time, a bit later on, when somebody damns your soul for the last time.


If it’s a solid extension which could be used by other websites, and it’s explained clearly like in your post by the website which needs it, then probably yes.


Maybe because you can’t make sure the server uses the code it advertises without modification (The source code could be open and safe, but how can you make sure the website is actually using that?), while the extension is open source and could be downloaded directly from Github by the user. And if enough websites start using this system, it could gradually stop being an extra extension for that one website.
WDYM Libadwaita is not customizable? Libadwaita is the most customizable UI lib I would say. You literally can just change every part of any app through css and call it a day.
I haven’t tried doing it in a while, but I remember it being very difficult to change themes beyond tint and colors, with lots of apps having custom colors not in the pallet used in the “gtk.css” file.
Gnome is great.
Most Linux users can’t deal with every single project not prioritizing customization. Gnome having a unique workflow (which is a great one) is unbearable for some reason.
I am not gonna place the full blame on the Linux community though. Gnome started out way more customizable, so maybe that suddenly getting pulled from underneath Gnome users so inconsiderately gave it a bad reputation.
Then they went and did absurd things with libadwaita to not only stop supporting customization, but actively interfere with people’s choices of customizing Gnome and libadwaita apps so apps ~“are viewed and used as intended by their developers, and people don’t accidentally break apps and complain to the devs” (i.e. Bullshit).
Literally the only foundation that made Linux usable, stable, unified and customizable.
I really can’t see how. It’s popular and user friendly, but I can’t seriously give it that much importance.
For me at least: It just serves to show that Linux UIs can be clean, consistent, and user friendly. Which might pull in funding from companies and governments looking for a good UI to mass deploy.
But if it didn’t exist, Plasma would’ve eventually filled that vacuum.
Some people don’t like snaps
“Some people like snaps” would have been closer to the truth, but it would still be an exaggeration of their numbers.
Or make your own package? call it affirm (more wholesome), write it in Rust (of course), and take on yes.
Yes, OP has a problem with this part. You’d have to trust the website to serve you the clean client side JS each time you use it. The proposal requires you to check the source code (which is plain un-minified JS) of the extension to make sure it’s doing what’s advertised when you download it the first time and with each update, instead of having to check the client side (obfuscated / minified) JS of every website each time you use it.
That’s true, but auditing that one extension (even on every update), which may be used by other websites in the future, giving it more attention and audits, is a lot easier than checking the client side JS of every website.