turns out switching from gnome to KDE on fedora is *really easy* https://docs.fedoraproject.org/en-US/quick-docs/switching-desktop-environments/

[lritter@mastodon.gamedev.place]

@aeva what if the touch screen is 1" x 1"

[aeva@mastodon.gamedev.place]

@lritter a pen wouldn't work here though because my use case in the singular correct obvious thing to do with multi-touch screen which is to use it to make polyphonic instruments

[aeva@mastodon.gamedev.place]

@lritter magic. I'll take 100 of them

[lritter@mastodon.gamedev.place]

@aeva you'll get ONE (production shortage)

[lritter@mastodon.gamedev.place]

@aeva yeah that's... a completely legitimate and very cool application.

[aeva@mastodon.gamedev.place]

@lritter <3

[lritter@mastodon.gamedev.place]

@aeva with some transparent nubs on screen you'd even have finger guides to play it sightless

[aeva@mastodon.gamedev.place]

@lritter I wonder if chopping up a screen protector might work for that. At any rate, totally attainable, it just seems that one simply needs to first write a wayland compositor from scratch or somehow convince the people who make them to stop making bad decisions

[datenwolf@chaos.social]

@aeva @lritter

Stop using Wayland. It's a shitty protocol designed by people who didn't/don't knew/know what they're doing.

Heck, just recently I came across a Mesa driver developer who openly demonstrated, that they were clueless about how desktop compositors do work. Conversely a lot of desktop compositor developers are totally clueless about how GPUs work.

I challenge you to browse through the OpenGL related part of Hyprland, and take the time until you start to slap your head or vomit.

[lritter@mastodon.gamedev.place]

@datenwolf @aeva "stop breathing, air quality is not good"

[aeva@mastodon.gamedev.place]

@datenwolf @lritter I need you to understand: I. HATE. WAYLAND. WITH. ALL. MY. HEART. AND. I. HATE. EVERYTIHNG. THAT. LED. TO. ME. USING. IT.

[lritter@mastodon.gamedev.place]

@aeva @datenwolf what's the reason why you can't use it through a glovebox like SDL3?

[aeva@mastodon.gamedev.place]

@lritter @datenwolf what

[lritter@mastodon.gamedev.place]

@aeva @datenwolf i said: what's the reason why you can't use it through a glovebox like SDL3?

[aeva@mastodon.gamedev.place]

@lritter @datenwolf I don't understand the question

[lritter@mastodon.gamedev.place]

@aeva @datenwolf maybe i make too many assumptions. do you hate wayland as a user of apps that run on wayland, or do you hate wayland as developer who has to interface with wayland?

[aeva@mastodon.gamedev.place]

@lritter @datenwolf yes

[aeva@mastodon.gamedev.place]

@lritter @datenwolf I'm not using it directly, but writing stuff for it indirectly is awful

[aeva@mastodon.gamedev.place]

@lritter @datenwolf because wow what a choice, use the ~protocol~ directly and get a ton of busy work dumped on you *or* introduce a bunch of dependencies that all make assumptions on your behalf about what a normal application does and you have to live with every mistake the layers below made for you

[lritter@mastodon.gamedev.place]

@aeva @datenwolf fun fun. i'll be in that spot soon, too.