Oh, sorry for the late answer. I use a mobile client without notifications. ^^ From your other answer it seems you probably already know more than I do. ;)

Afaik they have their own repos but because of there being fewer people working on it, they often drop packages with systemd dependence instead of patching them, correct?

Oh, I tried Debian several times and it’s so much harder than CachyOS, especially concerning package availability. If Debian gave me headaches, Devuan will not be better, right? ^^

It’s definitely a me issue, but just to elaborate: A lot of stuff that’s in the CachyOS standard repos isn’t even available in Debian’s repos (and therefore probably the same is true for Devuan), so you have to add additional repos or compile from source (examples I ran into: julia programming language, Niri window manager, Noctalia “shell” (in the sense of a graphical desktop environment, it’s not a terminal emulator)). Don’t get me wrong, I can of course follow guides to get things done or settle for another software… But when I follow guides to force non-available software into Debian, I often have the feeling that I risk breaking things in the long term (e.g., how should I do updates of the stuff I compiled from source?) because I don’t really know that much about the system. Right now, sadly, I don’t have the energy to learn all of that. :'(

Absolutely. I was also thinking about trying a non-systemd distro. But I fear I’m not yet ready to hop into a system that I have to configure myself from the bottom up. If there was a well-configured “out-of-the-box” distro like Mint or CachyOS based on Devuan, Artix or Void, that would be so great.

That’s why I told you. :) Sorry that it won’t help you because of systemd dependence.

Oh shit, didn’t know that, thanks. :(

But it turns out that SDDM, the QT based login manager that’s meant to use with KDE

SDDM is Plasma’s “old” login manager. They phased it out in favor of the new Plasma login manager a few months ago. I don’t know how recent Void’s packages are, but I think I remember it being a rolling release, right? On CachyOS the switch was a few months ago.

In other languages that shouldn’t be equal either though, right?

Maybe you meant

if (2){
console.log("nonzero ints are truthy")
}
else {
console.log("no they're not")
}

Which would output

nonzero ints are truthy

and that would actually work in all languages I know. But that’s different from being equal.

It’s not. Just tried in my Browser Console:

2 == true // returns false

Mh, ‘0’ is a nonempty string, so !‘0’ returns false. Then of course !(!‘0’) would return true. I’d absolutely expect this, Python does the same.

And the second thing is just JavaScript’s type coercion shenanigans. In Python

bool('0') # returns True because of nonempty string
bool(int('0')) # returns False because 0 == False

Knowing that JavaScript does a lot of implicit type conversions, stuff like that doesn’t strike me as very surprising.