

No. This one is actually cool, useful, and innovative. And it tries to do some things differently than everyone else.


No. This one is actually cool, useful, and innovative. And it tries to do some things differently than everyone else.


Not knowing about opt-in telemetry doesn’t convey lack of experience, or lack of (relevant) knowledgeability. Especially considering the fact that Arch purposefully keeps the existence of it low-key to avoid the possibility of pissing off anyone.
I was already an Arch user when that opt-in telemetry was introduced. And only heard about it because I was relatively active in Arch communities back then (relatively young, relatively new to Arch). If pkgstats were introduced two years later, I would have never heard of them. Because believe it or not, Arch is just a reliable OS, where you don’t have to interact with anything other than reading the odd announcement every other year. It’s not a “community”, or a “way of life”, or anything in that bracket.


The premise of the question is wrong, since it assumes a general preference.
If you’re asking 👉 this 👈 Arch user, the answer is “NONE”.
EDIT: The majority of users, especially experienced ones, don’t enable pkgstats. So such stats always end up in some form of self-selection (biased towards users who would use a DE in this case).


They know you can just do if ((age < 18)) in bash, right?
Or rather if ((10#$age < 18)) because age=021 would not be adult 😉 Hopefully, they protect against that at least.
(I had to double-check this stupid default is still a thing, since I moved to zsh many years ago.)
sublemmy
Lemmy communities. Mbin/kbin magazines.
(didn’t read OP, didn’t keep up with chimera recently)
From the top of my head:
The init system. Usable FreeBSD utils instead of busybox overridable by gnu utils (which you will have to do because the former are bare-bones). Everything is built with LLVM (not gcc). Extra hardening (utilizing LLVM). And it doesn’t perform like shit in some multi-threaded allocator-heavy loads because they patch musl directly with mimalloc. It also doesn’t pretend to have a stable/release channel (only rolling).
So, the use of
apkis not that relevant. “no GNU” is not really the case with Alpine. They do indeed have “musl” in common, but Chimera “fixes” one of the most relevant practical shortcomings of using it. And finally, I don’t think Chimera really targets fake “lightweight”-ness just for the sake of it.