developing an app directly on wayland and that it would be really difficult.
yes it would - you'd just end up reimplementing work from projects like SDL and gtk, this is why we invented libraries.
firefox and gtk
firefox is gtk3 based, which is substantially different from gtk4, and moreso adwaita. there's some discussion about porting to gtk4, but for large projects like these shit is slow moving - just look at how long steam is taking to port their client to wayland.
And yet most gnome apps use context menus... They're just not a priority given that any functionality in a context menu needs to be duplicated elsewhere so that people can find it. This isn't just a gnome thing btw, it's the way UI everywhere is going: Hamburger menus all the way down.
bottles
I like it, i use lutris though because i don't care for the sandboxing.
the right mouse button is never used for anything?
I'm curious, what exactly would you want RMB to do? And the reasons why it's not used much is twofold, lack of discoverability and touch based device compatibility (which isn't just phones btw).
You only "need" extensions if you want them. GNOME by default is its own thing that's pretty different from win11 and kde - everything goes through the overview, things like desktop icons and dash to dock break the intended experience.
Not everything has to be romantic, true enough, but not having any romance at all is a problem too. For example in your scenario, 15 year olds are teenagers going through puberty and they will be horny, continuing just because they're dealing with life and death doesn't stop that - people in the military certainly don't abstain from sex.
The pitt doesn't show much romance on screen, but it's constantly there in the background, with pretty much every character being driven by their ongoing relationships or lack thereof.
The main reason Valve doesn't step in is because it would cost them money. Moderating content is expensive as hell and these corporations will bend themselves backwards finding any and every way to avoid it.
KDE is relatively smaller in scope than GNOME. Besides, GNOME has taken on its own hurdles like compatibility across devices, the userbase is also different so they're less likely to contribute towards areas like gaming for example.
What lets GNOME dominate developer wise right now are adwaita and the language barrier - KDE is mostly c++, whereas in GNOME you'll find a mix of languages and outreach programs like GNOME circle.
You gotta load up Gnome with hundreds of extension
You don't have to though? I use vanilla GNOME.
Customization is never free, if you aren't using it it's just bloat and the more you add the more it slows down development.
KDE is following GNOME in dropping x11 support in early 2027. The only solution if you want to still use x11 going forward is to get a LTS like ubuntu and bunker up for the next 10 years.
Wine has been able to run on wayland for a while now, though upstream wine uses a different wayland pipeline than proton-ge that uses em10/wine-wayland.
