It’s not stupid insofar that it is an additional fingerprintable data point. But it’s obviously still much harder to fingerprint you if many users share the same value that you have, so it is invalid.

You’re approaching this with an everyday definition of “proposal”, but in the industry that term is overloaded with more specific meanings.

If you asked 100 random devs, I have no doubt that the majority would call a PR to be something much more concrete than a proposal.

At least that’s usually an honest mistake, instead of some managers trying to juice their numbers through dark patterns.

Unless, of course, you’re using Ubuntu. Then it might also be a manager trying to juice their numbers.

The Lemmy API has started to change, causing some features to not properly work anymore (e.g. Marking as Read hasn’t been properly working for months) and some content to become inaccessible (some posts and some comments just don’t load anymore, especially noticeable with “error 17”).

That’s not to mention that new features simply won’t be available, e.g. all the new stuff mentioned in the last release notes.

Boost is a great option! I’ve personally switched to Summit, but we’re really lucky to have many great app options available on Android.

This would undoubtedly, unquestionably happen, and it would break JSON. The only reason it works so well is because comments aren’t allowed.

Is there a reason? Norway!

Even then there’s rarely a good reason to use inheritance instead of composition.

It’s pretty much undeniable that the GPL has been a massive driving force behind companies giving back to projects, and it’s similarly undeniable that MIT-licensed projects have fewer comparable contributions.

Sure, the community can stay on the open version, but it will still be companies mostly taking without giving back.

I’m on version 0.0.0.0.0.0.0.0.0.0.0.0.0.1 already!

I’m not saying you’re wrong on all or even most points, but just by itself this comment is basically a marketing post.

KDE is relatively smaller in scope than GNOME.

By what measure, and which parts of the projects are you taking into account?

Besides, GNOME has taken on its own hurdles like compatibility across devices,[…]

KDE has also taken on its own hurdles. By the way, compatibility across devices is one of the best examples of feature creep if you don’t need it, as most Desktop users don’t!

[…]the userbase is also different so they’re less likely to contribute towards areas like gaming for example.

Don’t see how that’s relevant to the development speed of the environments and their customizability.

What lets GNOME dominate developer wise right now[…]

Again, by what measure? Does it result in faster development of helpful features for my workflow?

[…]and outreach programs like GNOME circle.

KDE also has outreach programs, so this also doesn’t show much.

The development of KDE doesn’t seem any slower to me than Gnome. But it does support my workflow much better due to the customization options!

When using gamescope, there’s also --force-grab-cursor: https://wiki.archlinux.org/title/Gamescope#Cursor_doesn’t_behave_properly

I don’t understand how they’re still doing it. This is literally the reason I see most often for people turning away from Ubuntu.

They must really expect to be able to thoroughly enshittify Snaps, otherwise it can’t be worth it for them.

and one bug that was quickly caught and fixed

The performance regression? It hasn’t been fixed.

You know - when you list two points, and I refer to those two points in my response, maybe assume that I’m responding in the same order you listed?

Actually that is not too far off from being true.

No, it absolutely is very far off, unless you find actual studies & user feedback. Lets not do weird mental gymnastics to find logic in pure hyperbole. You gotta give me way more than one 1-week-old bug, and one bug that was quickly caught and fixed. Bugs are going to happen in software that is worked on.

The reason X was stable for a long time is because many new & nowadays important features (like fractional scaling) weren’t being worked on, the ecosystem was mostly frozen. There’s more churn around Wayland because it’s newer & supports more (and often structurally much better) approaches to solving its problems. Don’t want to get caught in that? Maybe don’t use a distro that is specifically known for shipping new software very quickly.

Ah yes, I forgot that all Nvidia users also use their internal Intel graphics card. How could I?

Ah, if it’s not working right for you, it obviously means it’s not working right for 60% of people.

What’s that? The situation has improved dramatically over the last two years, and many happily use Nvidia cards with Wayland without issues, me included? No, can’t be the case, you still have issues.

Maybe because it doesn’t suck anymore on 60% of graphics cards?