>>159 I know what an X server is. I just want to run my Window Manager without tearing or a heavy compositor. I don't care about some proof of concept X server that will be never finished. I have two options Xlibre or Xorg compiled from source. If distributions don't want to provide Xlibre for some reason (at most the Xlibre dev is some "I don't see color" boomer, there's a Nix rice with LGBTQ+ flags on the github readme. Yes it's cringe but how many Zionists do you think there are that have contributed to Emacs for example). All the reasons you shit on systemd for can be applied to Xorg. Xorg has tools to control a plethora of things while on Wayland it's the compositor which chooses (or doesn't) to implement these features and most Wayland compositors kinda suck or don't implement all of these features. If I wanted to switch from EXWM to a Wayland compositor I'd use EWM which was recently bootstrapped with Claude while EXWM has been around for years and has a bunch of useful packages like exwm-edit. Also what's the security benefit from Wayland when it's all dependent on how the compositor is implemented. Are huge desktop environments like GNOME or KDE safeS Is a recent compositor made with the help of AI safe? Or do I just take the theoretical security risk and continue using my Window Manager that already works for me? The Pure-GTK version of Emacs is slower than X11 versions of Emacs ON WAYLAND! Not even accounting the difference between Emacs with alternative toolkits like Lucid which work better for remote workflows this is a point for both X11 itself and non-GTK versions of Emacs. >>157 Why should it they explicitly mention this and ship their own repos. If you're using Arch's repos you're own your own. I'm not an Arch user or like that the base repo is smaller and you're reliant on random scripts. Nix and Guix are already easy to package for yourself and Nix is larger than the AUR. But I know there's a learning curve and some people like the traditional way of doing things. Artix actually packages alot of services for alternative init systems that you could use on other distros after some manual work and their repos contain some software not even in the Arch repos. >>158 Rephrase: I mean there are other init systems that implement the features of systemd without all the baggage. The closest is dinit. It's great if runit works for you or you have some a list of init scripts that you've been writing yourself.
I know what an X server is.
I just want to run my Window Manager without tearing or a heavy compositor. I don't care about some proof of concept X server that will be never finished. I have two options Xlibre or Xorg compiled from source. If distributions don't want to provide Xlibre for some reason (at most the Xlibre dev is some "I don't see color" boomer, there's a Nix rice with LGBTQ+ flags on the github readme. Yes it's cringe but how many Zionists do you think there are that have contributed to Emacs for example).
All the reasons you shit on systemd for can be applied to Xorg. Xorg has tools to control a plethora of things while on Wayland it's the compositor which chooses (or doesn't) to implement these features and most Wayland compositors kinda suck or don't implement all of these features.
If I wanted to switch from EXWM to a Wayland compositor I'd use EWM which was recently bootstrapped with Claude while EXWM has been around for years and has a bunch of useful packages like exwm-edit. Also what's the security benefit from Wayland when it's all dependent on how the compositor is implemented. Are huge desktop environments like GNOME or KDE safeS Is a recent compositor made with the help of AI safe? Or do I just take the theoretical security risk and continue using my Window Manager that already works for me? The Pure-GTK version of Emacs is slower than X11 versions of Emacs ON WAYLAND! Not even accounting the difference between Emacs with alternative toolkits like Lucid which work better for remote workflows this is a point for both X11 itself and non-GTK versions of Emacs.
>>157
Why should it they explicitly mention this and ship their own repos. If you're using Arch's repos you're own your own. I'm not an Arch user or like that the base repo is smaller and you're reliant on random scripts. Nix and Guix are already easy to package for yourself and Nix is larger than the AUR. But I know there's a learning curve and some people like the traditional way of doing things. Artix actually packages alot of services for alternative init systems that you could use on other distros after some manual work and their repos contain some software not even in the Arch repos.
>>158
Rephrase: I mean there are other init systems that implement the features of systemd without all the baggage. The closest is dinit. It's great if runit works for you or you have some a list of init scripts that you've been writing yourself.