turns out switching from gnome to KDE on fedora is *really easy* https://docs.fedoraproject.org/en-US/quick-docs/switching-desktop-environments/
-
@aeva what if the touch screen is 1" x 1"
@lritter magic. I'll take 100 of them
-
@aeva you'll get ONE (production shortage)
-
@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 yeah that's... a completely legitimate and very cool application.
-
@aeva yeah that's... a completely legitimate and very cool application.
@lritter <3
-
@aeva with some transparent nubs on screen you'd even have finger guides to play it sightless
-
@aeva with some transparent nubs on screen you'd even have finger guides to play it sightless
@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
-
@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
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.
-
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.
@datenwolf @aeva "stop breathing, air quality is not good"
-
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.
@datenwolf @lritter I need you to understand: I. HATE. WAYLAND. WITH. ALL. MY. HEART. AND. I. HATE. EVERYTIHNG. THAT. LED. TO. ME. USING. IT.
-
@datenwolf @lritter I need you to understand: I. HATE. WAYLAND. WITH. ALL. MY. HEART. AND. I. HATE. EVERYTIHNG. THAT. LED. TO. ME. USING. IT.
@aeva @datenwolf what's the reason why you can't use it through a glovebox like SDL3?
-
@aeva @datenwolf what's the reason why you can't use it through a glovebox like SDL3?
@lritter @datenwolf what
-
@lritter @datenwolf what
@aeva @datenwolf i said: what's the reason why you can't use it through a glovebox like SDL3?
-
@aeva @datenwolf i said: what's the reason why you can't use it through a glovebox like SDL3?
@lritter @datenwolf I don't understand the question
-
@lritter @datenwolf I don't understand the question
@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 @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?
@lritter @datenwolf yes
-
@lritter @datenwolf I'm not using it directly, but writing stuff for it indirectly is awful
-
@lritter @datenwolf I'm not using it directly, but writing stuff for it indirectly is awful
@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 @datenwolf I'm not using it directly, but writing stuff for it indirectly is awful
@aeva @datenwolf fun fun. i'll be in that spot soon, too.
-
@datenwolf @aeva "stop breathing, air quality is not good"
-
@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
@aeva @datenwolf SDL has so far always been pretty good about giving me options. glfw not so great. not great at all, in fact. raylib probably even worse. but perhaps you need something even SDL can not provide.