transcription: be me, closeted transfem, have computer science degree, family constantly bothering me with tech problems, always dumb shit like not restarting computer or googling error messages, lightbulb.jpeg, come out to family, get disowned as expected, they never contact me again, dont have to deal with their dumb it problems anymore, mfw, should have done this years ago.

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 3 days ago (1 child)

I think the main stability issues that people encounter with Wayland are because of one of two reasons:

  1. Dogshit nvidia drivers that dont support Wayland
  2. Wayland has added security features, and the program you're using doesn't support them.

The main security features people get hung up on are:

  • screen sharing
  • clipboard
  • stealing window focus
  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 3 days ago

    There's some other problems, some more stupid than others

    • GNOME refuses to support clientside decorations, the Wayland specification doesn't require it, so any software that wants to work in a window and support all major DEs needs to have code to draw its own titlebar
    • I think screensharing still has some problems that haven't been settled yet, not sure if there's a way to capture an application and only its audio, might work worse for preserving capture configuration across restarts
    • Global hotkeys have a somewhat stupid issue, and OBS refuses to support them - the issue is that OBS supports having multiple profiles and wants to be able to have different hotkey bindings for every profile, and there's no good way to do that right now.
    • Global hotkeys also have a controversial side in that there's no consistent way for applications to know what keys are bound to hotkeys, and application developers want to display hotkeys inside application settings and allow users to change them there. And that's an issue because Wayland developers want to ensure Wayland isn't restricted to only typical keyboard, mouse, gamepad setups, and things like global hotkeys can be bound to things like touchscreen gestures without needing workarounds like emulating keypresses.
    • Another issue in a similar vein is window positioning. Some software opens multiple windows, and its developers want to be able to position those windows in a layout. On the other hand, Wayland developers don't want to limit software to rendering on rectangular 2D screens, and don't want software to be positioning windows with 2D coordinates like that, and instead have a way for software to indicate to the compositor more semantically how windows are meant to be laid out. I don't think they've worked out a solution yet.

    I respect Wayland trying to avoid backing itself into a corner where expanding future support is going to be a mess because they rushed to get something out, but it does take a long time, and we're not there yet.

    On a somewhat random note, I have a screen with probably crappy HDR support, and previously on Plasma I tested it a couple of times for fun, but there wasn't much support from software and the colors were off. Recently I hit some weird bug where my colors were just off (on SDR), looking greenish, decided to try turning HDR on and off to see if it'd help. After turning it on, I realized the colors look fine, after running the calibration it looked the same as it would in SDR, but just with HDR support. I tested it on YouTube videos, not sure how to tell how well it's working, but it's a nice "huh, guess we got there" moment, where there's another thing that now just seamlessly works for me.

  • source
  • parent