But no vendor actually implements any with the exception of those forced to include APFS by Apple.

Actually some vendors implements NTFS driver in their UEFI as well.

I print recovery codes of all services and packed them into a bag.

That may be because the hostname can't be resolved.
https://forum.suse.org.cn/t/topic/12280 (Chinese)
https://bugzilla.mozilla.org/show_bug.cgi?id=1296836 (upstream report)

So use Fcitx 5 Android instead. It's a open source IME application without requesting any permission except Notification, especially without network permission.

https://github.com/fcitx5-android/fcitx5-android

• GNOME removing Server Side Decoration support in wayland.
• MultiMC author rejecting people build it from source by themselves although MultiMC is under Apache license.

There is a benchmark use https://webglsamples.org/aquarium/aquarium.html

https://blog.lilydjwg.me/2021/11/12/display-tearing.215968.html

• X11 + Intel card, 1080p 60fps, GPU fully utilized, one third of frames dropped! 4k 60fps is about the same. It turns out that the focus is not on the resolution (the GPU isn't used to its full capacity anyway), it's on the frame rate of the video.
• Wayland + Intel cards, 4k 60fps, not even dropping frames, let alone anything else, and the GPU is used for about half of the graphics calculations.

For hardware decode, when I switched to wayland, it was only implemented in Wayland. After they implememted EGL on X11, they implemented hardware decode on X11 as well.

For mixed DPI, applications can implement it use screen information, but not all applictions will do this. But wayland ask them to implement this feature.

It's reference implementation, but isn't suitable for daily use. Because it lacks some convenient features. It's used as a behavior reference when some one develop a new compositor.

For sans and serif font, Noto Sans and Noto Serif.

Always use absolute path. If you write some shell snippet which may be run in different environment, avoid use just command name for uncommon one.

exa has a terrible bug: if you set TZ environment variable to ':/path/to', you will get 'Unable to determine time zone: No such file or directory (os error 2)'. Does eza fix it?

https://github.com/ogham/exa/issues/856