Skip to main content


Whenever I see comments like this about #Wayland I always have to ask, who do you think would be developing this new protocol? Every single #Linux graphics developers agrees that Wayland is where we're going, the problem is nobody agrees on how it should look
in reply to Brodie Robertson

That may be *a* problem, but it's not *the* problem. *The* problem is that it's been made default almost across the board and isn't ready to be so. At least I don't think it is.
in reply to Brodie Robertson

I'm probably a victim of "it needs to work for me therefore doesn't work for a lot of people," but screen capture needs to be actually working. Also, more fully featured window managers (which is what I will always call them). That'll take time.

As for mainstream, better Nvidia support is obv. the big one. And application support is still really lacking, at least it is for me.

in reply to Brodie Robertson

@thelinuxcast I can only think of something like Regolith: https://regolith-linux.org/

All twms on x11 or compositors need a lot of configuration and tinkering.

in reply to Brodie Robertson

@thelinuxcast
With the recent discussion about the ext type protocols makes me wonder if there was ever a proposal for delegation of window management to a separate process while the compositor retained all other features.

May or may not be possible based on the design and security principles but plenty of other software has ways to offload processing to an external process and return results.

in reply to Brodie Robertson

@thelinuxcast I think we should focus on bringing back a universal method for apps being able to call Wayland directly for what application has focus as offloading that to the DE is really dumb & puts a huge amount of work on application devs that does not need to be there.

But to do that they have to create a privacy & security type gate (macOS) that requires users to approve that level of access to specific apps, & accessibility type apps need it too.

in reply to Brodie Robertson

@thelinuxcast imho if you have handicaps then x11 is the most realistic option as Wayland won’t do you any favors if you need accessibility features enabled & 3rd party apps.
in reply to Brodie Robertson

Who they think they are scraping others, open source and free, work? What's next? Enter in a Xorg conference with a toilet sink and bossing people around?
in reply to Brodie Robertson

Change is good, but change needs to be managed. I have a manjaro box with plasma and a choice of X11 or wayland session.

In the wayland session viewing images scaled in gwenview delivers images which are not properly scaled more like postage stamps in a sea of black. My customised favourite list is squashed and order change.

I've no idea if this is a plasma issue or wayland issue. I don't care, I just want it to work So X11 for now.

in reply to Brodie Robertson

@BrodieOnLinuxDo you know why is Wayland support with nvidia GPUs going to slowly? I can't even choose a Wayland session in the login screen.
in reply to Coin

@BrodieOnLinuxnigger support for any Nvidia is broken in current Linux kernels. I cannot boot my gentoo desktop unless I use nouveau. the kernel panics
in reply to anime graf mays 🛰️🪐

@BrodieOnLinuxSo I have to get fucked by GNOME since they're going Wayland only soon? I may have to move to KDE if that's the case...
in reply to Coin

@BrodieOnLinuxif gnome is dropping Wayland only they are going to burn the last of their userbase. you CANNOT game in Wayland. the environment is hostile to it. steam chose KDE because it's the most supported and steam is still anti Wayland. not sure what the push for Wayland is but gaming will decide where the Linux desktop goes. not gnome.
in reply to anime graf mays 🛰️🪐

@graf @coin GNOME is the biggest Linux desktop environment and the majority of there users already use Wayland
in reply to Brodie Robertson

I think Wayland seems to be built with software containerization in mind at its core, and it doesn't fit everyone
in reply to Brodie Robertson

I guess people hating #Wayland are the same folks that hate #SystemD or even #PipeWire whilst refusing to #DoBetter themselves:

#Toxic #Neighsayers that refuse to acknowledge that #Xorg, #SystemVinit and #ALSA / #OSS are bad.

Instead they create redundant work that noone cares and that only.pulls resources from improving mainlike #Linux.

Or does anyone use #Devuan in any busoness-critical applicationm?

Lo, thar be cookies on this site to keep track of your login. By clicking 'okay', you are CONSENTING to this.