My short answer:

Should I switch to Wayland?

Yes.

Applications that don’t cope with wayland still work via Xwayland. Go ahead.

If you’re not having performance issues, then I don’t see much reason to change. Sure, Xorg is basically in maintenance mode, but so what? Your setup works for you, so do your thing.

That said, Sway is a window manager intended to be a drop in replacement for i3 on Wayland, and is pretty close from what I hear: https://swaywm.org/

Plasma is very good with Wayland, although you might want to wait for Plasma 6, since they’re apparently making several improvements, and it’s due out soon anyway: https://www.phoronix.com/news/Plasma-6-Wayland-Great

You can install Wayland and switch sessions during login too, so you can check it for yourself and see if your i3 dotfiles work with Sway.

deleted by creator

I am no fan of wayland, but if it works the software you use and your workflow, then it would probably be advisable to do so. It is not for me and my day to day workflow.

The biggest Sin by far of Wayland is making users think about the graphics stack. Does this feature or this app support Wayland or X? Does this Compositor support this GPU? Does this particular environment support this mixture of displays with this DPI? Do I need to set a particular env variable or change a setting to force this app to start in Wayland mode because under X11 its scaled funky. What works in each environment? What doesn’t work between environments?

Well before you reach the end of this flow chart you have lost virtually all of your users. This transition has single-handedly set the Linux desktop back by 20 years in terms of supporting more users whose level of interest in configuration is limited to clicking a control next to their monitor and making things bigger or smaller.

A saner design would have handled scaling correctly from the start and would have had a permissive mode which just made everything from the users perspective work while progressively adding a correct UI to provide features like global hotkeys, screen sharing, only to those apps users had authorized like android. If it wasn’t a such a clusterfuck to use it would have had orders of magnitude more users much earlier in the development phase and perhaps attracted more development interest as well.

in my experience wayland is faster to log in and less input lag, problems are things like discord that don’t implement screen record, but it work on the browser, and sometimes i need to find replacement for some apps that work on wayland(like xdotool to simulate mouse etc) i use fedora so wayland is default

What are the advantages of Wayland?

The big one is proper support for diffrent refresh rate monitors and VRR. Also some security improvment and long term support (X11 probably has only a few years before development stops).

What are the disadvantages?

Its still a little buggy in some cases (especialy when using Nvidia hardware) but with an AMD or Intel GPU its more then usable. Some apps don’t play nice with Xwayland but its pretty rare.

How’s gaming?

I haven’t encontered any major issues with games. Some games might need launch parameters but usualy you can just google it and find the answer very quickly. Performance its exactly the same as on X (maybe even slightly better)

What would be the best way to switch?

On your desktop with KDE you can just select “KDE (Wayland)” in your display manager and KDE should just run like normal but with Wayland. On you laptop you’d need to switch to a diffrent WM since i3 dosen’t support Wayland. Your best bet would probably be Sway since its compatible with i3 configurations.

Why have you made the switch?

I wanted to check out how well Wayland works and found that it works fine for me, and so i decided to move. Also X was giving me issues with screen tearing and multiple monitors.

I’ve fully switched to Wayland some time ago (it could be already a year) after I learned about how insecure X really is and I honestly do not experience any issues that I sometimes see on the internet. I’ve been using Gnome for few months, but now I switched to KDE. I think a lot of apps are working natively on Wayland, but for other cases you have XWayland that also works flawlessy in my opinion.

One of things that was issue for me was that I couldn’t use Auto-Type feature in KeePassXC, because Wayland doesn’t let apps pretend to be a keyboard or capture windows as easily as X does. Funnily enough, I’ve managed to get it working by running keepassxc --platform xcb, but it stopped working some time ago and I’m not entirely sure why. Other thing that is a problem for me is screen sharing. Wayland doesn’t allow apps to capture screen as I mentioned earlier so it heavily relies on PipeWire for this and PipeWire has its own sets of problems. It seems working correctly for the most part, but I couldn’t really figure out how to share screen with sound. Not a dealbreaker for me, and a workaround would be to route audio as a microphone input for example, but it is an issue nonetheless. This is only a problem on Discord, in OBS you can easily select video and audio sources.

If you’re using KDE already, you could just select Plasma (Wayland) in your display manager and play with it a bit to see if you like it and experience any issues.

If it ain’t broken don’t fix it.

You should, and you will :) X11 is legacy, and is going to die. The only question is whether you’re going to try and hold on to a broken system riddled with security vulnerabilities for as long as possible until you’re forced to switch, or whether you’re just going to enable what is mostly already the default stack on most desktop Linux systems anyway.