The problem is not caused by mono kernel. Just because AMDGPU driver was developed in mono style. i.e. they include the code of all generations in one driver. In monolithic kernel, the developer can develop drivers with "micro" style. e.g. Intel's GPU driver doesn't use mono style, they created a new driver when they changed GPU hardware architecture.

Monolithic kernel is a concept about address space. If all parts of a kernel are running in the same address space, this is a monolithic kernel, otherwise it's a micro kernel.

This problem is about how to split parts, but not how to place parts in memory.

In my opinion, that's because X11 lacks proper abstract for many things like screenshot, screencast, color managerment and etc, so the applications have to use many X11 implementation details to implement these features. It leads to high-coupling code with X11 so move their code to wayland and ensuring it works correctly and is consistent with the old behavior is difficult.

Terraria

Yeah. Bitwarden developed a new android client written by Kotlin to replace old C# client. This new client is in beta testing currently. The old client supports both PascalCase and camelCase but the new client only supports camelCase. And Vaultwarden use PascalCase now, so it's incompatible with new Android client.

zsh, because of highly customizable.

Oh, my bad. But OpenGL ES 3.1 and Vulkan 1.2 is also not suitable to 2023. Hope the developers can make driver support Vulkan 1.3.

The way to support Nvidia 20x 30x 40x series GPU.

I use Porkbun.com. It has modern interface.

It may be related to Nvidia. Most bugs I met in Wayland is related to it. Such as no dmabuf export support, and vulkan init will fail because a bug in nvidia prime implementation...
As Linus said, so Nvidia, fuck you...

You should, I think. You don't have Nvidia GPU, so you can avoid almost bugs and get better performance.

Advantages:

1. Better performance. e.g. for Firefox, @lilydjwg got double performance in wayland.
2. Better multi-screen with multi-DPI support.
3. Better maintaince. Many DE has put more and more to wayland. And many new features will only be implemented in wayland. (That's because implementing many new features will be difficult or even impossible in X11 old software architecture, as KWin developers said.)

Disadvantages:

1. Some missing feature, such as remote desktop.
2. Many bugs when you use Nvidia GPU.
3. None of the compositors except KWin and Hyprland can use input methods with electron.

I don't know which DE/WM you use. If you use Plasma/GNOME, migration is simple, just switch in SDDM/GDM. If you use i3, you can try sway, it's compatible with i3 config. If you use others, you can try hyprland or wayfire. Wayfire has fantastic animations.

I switch to wayland because I buy a new screen with different DPI... But when I switched, I found I got better performance and video hardware acceleration in Firefox (this feature was introduced to Firefox Wayland first).

I just use ls, cd, tree and tab completion. Sometimes I will use rg to find files which contains specified string, and use locate to find files which I known name but path.

VP9 for video and FLAC for audio. Avoid AV1 because my GPU can't decode AV1.