481

X is just better! (beehaw.org)

submitted 5 months ago by chahk@beehaw.org to c/programmer_humor@programming.dev

64 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] Scoopta@programming.dev 59 points 5 months ago

As someone using Wayland I can confirm it's indeed not a hot a mess

[-] smpl@discuss.tchncs.de 16 points 5 months ago

Okay, but that would have made a shitty joke wouldn't it?

Hmm.. I don't know maybe it's fine as a joke.

[-] docAvid@midwest.social 5 points 5 months ago

Can I use AwesomeWM, XMonad, or StumpWM on Wayland?

Can I run a GUI program over ssh?

Does it support the X selection and clipboard protocols?

(These are not rhetorical questions, I'm really asking.)

[-] Scoopta@programming.dev 12 points 5 months ago

No you cannot run any of those WMs, some of those do have ports with varying degrees of completeness but only sway(i3) and hyprland(hypr) are ready for prime time.

Yes, using waypipe

Yes, primary selection does work along with Ctrl+c although as others have mentioned it forgets when the app you copied from gets closed

[-] fl42v@lemmy.ml 10 points 5 months ago

Can I use AwesomeWM, XMonad, or StumpWM on Wayland?

Can you run macos software on linux?

Can I run a GUI program over ssh?

This is more of a why would you... Although, waypipe

Does it support the X selection and clipboard protocols?

Too lazy to google, but overall clipboard works as expected, both C-c and text selection. I remember experiencing problems with clipboards in vim (like 2 yrs ago) which were fixed by switching to nvim

[-] Chewy7324@discuss.tchncs.de 5 points 5 months ago* (last edited 5 months ago)

Wayland only keeps the clipboard until the application exits. This means a clipboard manager is basically a requirement. Iirc desktop environments might solve those issues by default, but on a standalone compositor just add a clipboard manager and enjoy the history.

[-] fl42v@lemmy.ml 3 points 5 months ago

Correct, yet I personally don't find it too useful and sometimes harmful when dealing with, for example, password managers

[-] Chewy7324@discuss.tchncs.de 3 points 5 months ago

I've added a keybind for deleting history, but it'd be great to have a way to specify short lived clipboard entries. But this might also be one of those standards that no one implements.

[-] fl42v@lemmy.ml 4 points 5 months ago

Seconded. Although that very much depends on the compositor of choice: I've been trying out a few new shiny things (well, pinnacle, strata, buddaraysh), and they aren't exactly usable rn. With the exception of the latter one, probably (since the author claims to use it), but I haven't been able to start it so far... On the other hand, major players like hyprland and sway work perfectly fine on my machine :tm

[-] Adanisi@lemmy.zip 6 points 5 months ago

I'm on KWin Wayland, it also works great. I actually never noticed that I was switched from X11 to Wayland when I reinstalled Debian.

[-] Scoopta@programming.dev 3 points 5 months ago

I personally run sway. I was really looking forward to kiwmi but that project looks dead

[-] SomethingBurger@jlai.lu 3 points 5 months ago

OK cool. When will it support nVidia?

inb4 it's nShitia who must support Wayland

Wayland compositors run entirely in userspace and do not interact directly with hardware drivers. If Wayland doesn't work on nVidia but X does, it's a Wayland problem.

[-] Scoopta@programming.dev 9 points 5 months ago

Compositors do directly interact with the drivers though. The reason Wayland doesn't work on Nvidia is because Wayland uses an API called GBM(generic buffer management) to draw directly to the Linux VT. The Nvidia drivers don't implement that API, the API that both AMD and Intel drivers support. It very much IS an Nvidia problem and not the other way around. Nvidia tried to convince all the Wayland developers to use EGLStreams instead but no other drivers use(or even support) that API, everyone agreed on GBM except Nvidia. That's not Wayland's problem.