imecth

Ubuntu’s GNOME is quite different from the vanilla GNOME you’ll find in fedora.

deleted by creator

Extensions can crash your system on GNOME as they modify the shell itself, so running incompatible extensions is a real problem. The upside to this is that when you find an extension and it has your version on it, it’s guaranteed to run. Fyi you can easilly override the version requirements.

GNOME major upgrades (v48, v49…) always break extensions by design to force the extension maintainers to update. It’s generally recommended to hold off on upgrading for a few weeks to give maintainers time to update their extensions.

It’s against their interest to offer this as they have everything to gain by making you install their proprietary application and capturing you inside their ecosystem where they don’t have to compete fairly. Would Steam be in the position it’s in if you didn’t have to install it to download your games?

GNOME’s always been customizable with gsettings and extensions, the problem is that the options aren’t exposed in the user settings and in the case of the extensions they are only available through third party software. The upside to this is that the desktop environment is leaner which allows faster development and generally less bugs.

Why unfortunately? GNOME puts a lot of work in accessibility and being viable on every device.

How bad can it be? It’s just GNOME with a few extensions to make it look like windows.

As I explained elsewhere there is no official app to change this setting

You’re skipping a step here, first a decision needs to be made on whether or not the default will change, then and only then can they decide whether it’s worth adding something like a toggle to the mouse settings panel, which would be trivial btw.

You could always read the original source and find out the intent, but who has time for that?

Yes they actually review the extensions, you’ll find more information on the blogpost from last week.

GNOME manually reviews every extension, and they understandably don’t want to review AI generated code.

It’s disabled by default upstream as it’s still considered experimental, some distributions choose to override the upstream default.

Congratulations

Thanks. But in all seriousness i was trying to convey that your initial argument - experienced users not enabling pkgstats didn’t make much sense. It’s just funny in this case because you’ve been using arch for a decade and yet don’t know this basic thing.

Wouldn’t that mean the opposite - that you are actually not very experienced, or knowledgeable at least about arch? I’ve been using arch for a couple of years and “heard” of it just fine.

The majority of users, especially experienced ones don’t enable pkgstats.

Why would an experienced user not enable pkgstats? Anyways the biggest bias here is that arch inherently caters to power users which are going to have very different needs and likes than regular people.

Fractional scaling is a compositor issue, not a linux issue, so in this case kwin. But yes, fractional scaling in general is always problematic as there’s no way to cleanly multiply pixels by fractions, so you get wonky fonts, UI that doesn’t quite fit… and whatever hacks your compositor has on top to make it look better, it’s best to avoid it if possible and only increase the font size.

How is it a scam? They’re offering a service and asking for a price. It’s the same thing everywhere in software, if you want longer support you need to pay up.

Downstream distros are a bit of a special case, as they don’t really test these packages so much as inherit them from upstream, so what you’re actually getting is ubuntu’s and debian’s version of GNOME in Mint for example. If you’re going to do that, I’d just cut out the middleman and go upstream here as Mint isn’t bringing anything of value, worse it’s just another vector for untested bugs.

https://bbs.archlinux.org/viewtopic.php?id=297558. this is just the first thing that came up, i’m sure there are hundreds of similar bugs. bottom line is when you install two things next to each other that aren’t being actively tested together, you’re bound to run into issues.

My recommendation is that if there are no spin with your favorite DE, you simply do not use that distribution as it’s not being tested against.