Wayland chat

[teika]

EDIT: The original post was titled "If you have never tried Wayland, first read this". But the thread has evolved into a Wayland chat. ;)

Q: Should I migrate to Wayland?
A: Not yet, as of 2021. Probably you can live in X, at least, until the end of 2023.

Here's what users should know first before switching from X to Wayland.

From a user's point of view, Wayland is nothing more than a framework. In particular, Wayland itself does not implement any display server that should correspond to the Xorg server. In Wayland, compositors are display servers. Moreover, a compositor also serves as X's window manager (and X's compositor).

This means users first have to choose a compositor, and via that compositor they "configure the server", i.e. set screen resolutions, input and video drivers options, etc.

The situation however is not totally random, by being up to each compositor - many compositors depend on the library "wlroots", which abstracts such common tasks. See below for more details.

N.B. The Wayland project themselves provide the compositor Weston, which is a reference implementation (Wikipedia article) of the Wayland compositor. Though meaningful for developers, Weston is not really meant for users' daily use.

The library "wlroots" provides common compositor tasks. It is aimed to be "unopiniotaned". First started as a subproject of the compositor Sway, now it is used by many compositors. Exceptions include mutter and KWin, i.e. GNOME and KDE, and weston, which is a minimal, reference implementation.

Disclaimer
The above explanation may have loose ends. (I haven't tried Wayland at all.) Sorry beforehand, and I'll fix if you point out some. (And my English is far from perfect.)

Rant
The above is what I posted to Arhclinux Wiki just now. It is what I myself want to have read years ago.
Nerds have copied and pasted the cliché "Wayland is a protocol" (A) zillions times. It is a terrible self-satisfaction, and totally wrong, even if the sentence (A) is correct. I'm fed up with such people who don't know how to communicate.

Edit: Added the top question and answer. (8 Oct)
_________________
Hack of easy Shift / Ctrl / AltGr etc; save your pinkies, type without drudgery: topic 865313

BTRFS - Biden & TRump, Fools Suck.

[pjp]

Thanks for the clarification. I tried to use sway years ago and couldn't get it to work. Some day I plan to give "Wayland" another shot, but I'd prefer to use something like dwm. As I understand other explanations, it isn't possible for something as simple as dwm to exist due to how "Wayland" works.

Do you understand that issue well enough to clarify why it isn't possible?

I currently use i3, but only because I haven't gotten around to switching to dwm (and making some basics configurable without recompiling).
_________________
Quis separabit? Quo animo?

[Anon-E-moose]

[pjp]

Thanks, I'll at least take a look at the code to see if I can understand the basic differences. If nothing else that suggests progress from however old my "can't be as simple as dwm" information is.
_________________
Quis separabit? Quo animo?

[Anon-E-moose]

I've not used either dwm or dwl.

A resource list for various wayland tools/etc, https://github.com/natpen/awesome-wayland
_________________
UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland

[pjp]

Thanks. I've only used dwm briefly because configuring it requires modifying the code and recompiling it (my first goal would be to reduce that need). I'm mainly interested in it as I've long wanted to learn how to create a WM. dwm being minimal seemed like a good starting point. It's nice to know there's a similar reference point if X becomes untenable by the time the planets align.
_________________
Quis separabit? Quo animo?

[teika]

[Tony0945]

What is the purpose of wayland? Just "Not Invented Here"?
A more modern code implementation of the Xorg interface I could see. But throwing it all away, I don't.

[Anon-E-moose]

A wayland compositor is just like an X11 wm (some of which had compositing built in, for others an add on) but both are combined in a compositor.
But the compositor also takes on some of the abilities that the X11 server had (kbd handling, talking to "graphics engine", etc), which is a necessity since there is no centralized server.

As far as the purpose of wayland, think of it as an evolution of X.
Unfortunately there was no way to cleanly undo the spaghetti code that X has turned into over the decades, thus starting out a new path, I suppose in a way wayland could be called X v2.0 or maybe X v3.0.

Anyway, no one is being forced to use wayland over X, even on gnome/kde which prefer wayland, you can make it stick to strictly X.
_________________
UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland

[Hu]

[Anon-E-moose]

[pjp]

[Hu]

[pjp]

[JustAnother]

I got i3 and sway onto my computer.

The good news:
i3 can be viewed as a fallback position if sway is a problem, as the commands are basically the same. That is a positive when wants to use wayland, but also wants some insurance.

The bad news:
If you use a KVM switch as I do, the laptop video output must come from the VGA port, which is considered by the laptop internals to be a second monitor. In i3, one must use some xrandr command off a hot key to tell i3 to show the same output on the laptop screen and the external monitor port, or there will be headaches.

Sway does not allow xrandr, so so sway can be a problem if you have two monitors and want the same output. This is a very common need.

Both i3 and sway need a mouse click on an exit button to exit, but if the computer thinks there are two monitor outputs next to each other, the exit button can disappear. On the other hand there is a command line entry that will shut down i3 and sway.

The could be better news:
Basically, dmenu is problematical. It brings up all kinds of stuff that is unwanted and confusing. There is a graphic version of dmenu that puts all the gui app into the menu, bit this also feels like a miss.

In fact the idea of using a menu at the top to start applications is inconvenient, not to mention the monitor hassles which make it much worse.

What actually makes a lot more sense here is a simple text interface to launch applications. Much faster and easier to use, and it can be precisely tuned to work for you just the way you like. I wrote one, but it needs more work.

[Anon-E-moose]

For sway and all other wlroots based compositors, use wlr-randr although I prefer wdisplays (nice graphic layout w/randr abilities)
Or use kanshi (kind of like autorandr) which is what I use, with options for when I turn on my second monitor, that will auto switch when it sees it turned on.

If going straight wayland, I'd probably opt for sway vs i3, as I'm not sure how good i3's wayland experience is. Sway was designed for wayland from the start.

Menu's depend on which version of which package one uses. I prefer fuzzel, but there's plenty of alternatives.
ETA2: I use both the guru overlay and wayland-desktop overlay because they have many ebuilds that haven't made it mainstream ... yet.

I also use lots of keyboard shortcuts (which I've always found faster than point'n'click, though it does require using memory muscle)

To do remote apps on the system require me to pass the -auth parm to the Xwayland server, otherwise it'll holler about permissions.
ETA: I just tried with ssh -Y laptop remote-command and it worked fine.
I also pass the dpi flag since I run a 4k monitor and X (even xwayland) is stupid in that respect.

When I started using wayland, I kept X as a backup for a few months, then when I was happy with wayland got rid of the X server (just run Xwayland for those apps that need it).

Having said the above, if one needs all the features of the Xserver then wayland isn't a replacement now, and may never be.
I don't expect Xwayland to gain much more of Xservers features, past what's already there.
As a wayland dev said "if you need all the features of X, then use X"

I wish there was a fvwm port of the wm to wayland, but it would require a rewrite as X is too entwined in fvwm's current code base.
_________________
UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland

[mv]

[teika]

Thanks all.

The motivation of the original post was that I thought it may be a good time to migrate to Wayland. (But as I doubted, it is likely to be another pain, as usual. Anyway no one wants to continue X apps development.)
What led me to think so was the news that emacs-28, the next release, will be capable of X-free by being pure-gtk. In fact, it's already (almost?) done in the upstream branch "feature/pgtk", which was not yet merged into the master branch, as of 6 months ago. (Sorry, dunno the latest status.) I don't know if emacs-28.0.9999.ebuild already has it, nor about others ebuilds in gpo.zugaina.org.

FYI: In Archlinux, there're several AURs of pure gtk emacs: [1][2].

[asturm]

[Goverp]

[Anon-E-moose]

Yeah, KDE still has growing pains, that may be addressed in the 5.23 series just released (how long to get to gentoo is unknown, asturm might know)

https://community.kde.org/Plasma/Wayland_Showstoppers

ETA: https://kde.org/announcements/plasma/5/5.23.0/
_________________
UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland

[Comrade_Stalin]

Has anyone dared to try the DWL, the Wayland rewrite of DWM?

https://github.com/djpohly/dwl

I'm very curious but it looks to be nowhere near mature at this point. Plus I just got my DWM config perfect for me, so starting over is a tall drink to swallow. I'm glad somebody is on the job, the suckless devs sure aren't gonna do it anytime soon.

Wayland is very interesting to me, but Sway being the only stable TWM for it is gonna hold me back from using it for a while, I imagine. i3/Sway are good pieces of software of course, I just can't stand non-dynamic TWM after playing with Xmonad and DWM.

Knowing how this usual goes, I'll probably try it out anyway.
_________________
I agree with the official state-sponsered narrative and are therefor entirely neutral and unbiased.

[CooSee]

i love sway (wayland)

using freshly installed sway only system with tinydm via autologin.

then swaylock starts and locks automatically and acts like a login-manager

everything's great so far, very smooth, way faster than xorg, even 0ad is performing better.

from now on i refuse to use anything else

greetings (... programs)
_________________
" Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier "

[JustAnother]

Does anybody have any insights as to the upkeep of these, ahem, more mature browsers like lynx, links and elinks, and their ability to show images and graphics?

I'm all for the newest and greatest stuff, unless it doesn't work. This is my philosophy about new appliances. New cars too.

[389292]

Proof of concept is done. Now someone should just rewrite all X11 tools for Wayland, and we'll be set and ready to switch.
Maybe, while you at it, rewrite coreutils to something leaner as well, GNU is quite ugly actually. I think you can spare linux itself for now.