Conversation

Notices

1. Embed this notice
   Athanasius (athanspod@social.linux.pizza)'s status on Sunday, 26-Jul-2026 20:01:39 JST Athanasius

   RE: https://hachyderm.io/@whack/116983168997530856

   Oh my, I didn't realise the state of develop-for-Wayland was this bad. As a sometimes hobbyist developer I can feel the pain.

   It really does feel like one of the Linux non-profits could usefully somehow "take ownership" of the protocol level to at least standardise on one way to do things like virtual keyboard input. You'd think at least Gnome and KDE could have saved both their selves some time by co-operating on these things.

   I'll continue with Xorg-based X11 until there's good reason not to. Yes, I know about recent security issues, lack of maintainer-ship, and the shit show that has been the forks/alternatives...

   ... but my current X11+fvwm3 setup *works for me*.

   #wayland #linux #x11 #xorg

   • ?? Humpleupagus ?? repeated this.
   • Embed this notice
     一色いろは (wzqtparor@fedibird.com)'s status on Sunday, 26-Jul-2026 20:01:37 JST 一色いろは

     in reply to

     Wayland is fundamentally broken.
     I won't use it for 2 simple reasons:
     1. All wayland compositors are crashy and super unstable. My Xorg setup can have uptime over one year, while every compositor I tested can't survive one single day.
     2. libinput is a piece of garbage, lacks basic configurations, and every singe wayland compositor depends on it.
     @AthanSpod

   • Embed this notice
     ?? Humpleupagus ?? (humpleupagus@eveningzoo.club)'s status on Sunday, 26-Jul-2026 20:02:27 JST ?? Humpleupagus ??

     in reply to

     • 一色いろは
     Nearly two decades and it still doesn't work. They should just throw in the towel.