What is the very best Linux Distro? - best to make a poll about that

Best Distro

  • Total voters
    151
On the old test hardware I have Arch installed, and the server is currently running Debian. I am not complaining about both, because they do their job.

Also about, DE, I will be the guy who uses Gnome because unfortunately I'm used to it and It's hard for me to change, but maybe it's time to break the ice and install something else.
 
  • Like
Reactions: Creative Username
użytkownik said:
I am not complaining about both, because they do their job.
Click to expand...
It's kind of retarded to have a "favorite" distro, because the best distro is one that specifically gets out of your way and lets you do your work.
Broke Ass Centrist said:
The UI doesn't even fucking work half the time
Click to expand...
it's called GNOME. GNOME is fucking retarded
TheDataHorder said:
none.

it depends on your flavor of autism.
Click to expand...
Flavors of autism, flavors of Linux... Are they not the same?
 
  • Agree
Reactions: Sandy Sun Dunes and Betonhaus
Broke Ass Centrist said:
yeah sure, but GNOME isn't responsible for System 76's own fuckups, which are the problem half the time.

ffs they haven't even fixed the wine file association bug that's been in ubuntu for like 3 years now.
Click to expand...
Sounds like something with your hardware. Been using Pop as my daily driver for three years now and have never had any UI issues.a
 
  • Thunk-Provoking
  • Disagree
Reactions: Ether Being and The Black Hand
snov said:
All of these options are garbage, only NixOS is acceptable.
Click to expand...
I've used it for over a year now. I like the declarative configuration however I feel like most of what I learn won't be applicable elsewhere due to being built on non-standard abstractions of abstractions.
 
  • Like
Reactions: Basil Julep and Ether Being
seri0us said:
I've used it for over a year now. I like the declarative configuration however I feel like most of what I learn won't be applicable elsewhere due to being built on non-standard abstractions of abstractions.
Click to expand...
You will never need to unlearn it because it’s the future of operating systems. Other distros won’t even exist in five years, Windows and OSX will be gone in ten. NixOS supreme.
 
  • Optimistic
  • Dumb
  • Thunk-Provoking
Reactions: SCV, rareblacklobster, Ether Being and 3 others
I've been daily driving Mint for two and a half years. I have never had a problem I haven't been able to solve on it and I'd never go back to windows. I've been playing morrowind on openmw the past few weeks and it's been a blast. The only thing I miss is FLStudio. I've been thinking of virtualizing win10 for that but I'm a bit nervous about fucking up my OS with some sketchy ISO and the cracked FL exe I have.
 
  • Feels
Reactions: Ether Being
Broke Ass Centrist said:
Desperately want to switch to Linux Mint, Pop OS is trash and is the worst choice i ever made in regards to linux shit. The UI doesn't even fucking work half the time
Click to expand...
Newer versions of Linux Mint appear to have less functionality than previous versions and some annoying changes.
 
Depends on what you're using it for and your own personal preferences.

For desktop. I prefer anything Debian based with a lightweight desktop. (I3WM)

For headless server, I always use Suse.

Manjaro is by/for niggers. Updates cause it to break so often that it had to include a "system restore" feature ("timeshift") like windows, that endlessly eats hard drive space.
 
  • Like
Reactions: Creative Username
Honestly, a distro is just a package manager and maybe a kernel. I'm good with any distro that doesn't have Systemd, really. But, if I had a gun to my head and was told to pick the best distro, I would probably say Gentoo, because of the high degree of control that Portage affords the user.
 
Last edited:
  • Agree
Reactions: Ether Being
I'm Retarded? said:
slightly talking out of my ass here, any nerds with higher power levels feel free to correct me.
Click to expand...
Lennart Poettering
Lennart_poettering.jpg

Lennart "wontfix" Poettering is a German software engineer formerly employed at Red Hat, currently Microsoft. He rose to notoriety by creating PulseAudio which is a piece of shit/software intended to kill you by cardiac arrest by randomly blowing your speakers out.
Screenshot_20231111_233002.png
Following his initial success at garnering hate from large swathes of the Linux community he set out to give your system digital cancer by creating systemd and setting it loose upon the world. This has upset many people, but one must admit that it has quite perfectly mimicked actual cancer in both adoption and growth. Through his work on systemd Lennart became the proud winner of the 2017 Pwnie for Lamest Vendor Response [A].

Lennart has a narcissistic personality as evidenced by his propensity for downplaying bugs and vulnerabilities, not caring about breaking conventions or other pesky nuisances standing in his way, and naming himself Pid Eins (blog, Xitter). What is a Pid Eins? pid 1 (Process ID one) is the first user-mode process, init, that manages all other services on the system. You could say that pid 1 is the init system. This is what Lennart Poettering fancies himself to be; the process supervisor and service manager; the almighty arbiter. He obviously believes he can do an equal to or better job than most Linux developers as he has embarked upon a Not-Invented-Here crusade of recreating/reinventing every system service known to man as a systemd component.

It is my opinion that he is also a crybully. I'm not going to elaborate.

Systemd

Systemd is known for its complexity and unpredictability. I borrow/steal/repeat this line verbatim from skarnet because systemd is known for its complexity and unpredictability. Systemd can be fast to boot compared to a "traditional" init system as it can start processes in parallel. It may cheat by ignoring some dependencies in order to start things even faster; systemd is known for its unpredictability. Systemd can also eviscerate your boot time in circumstances when retarded stars align (e.g. waiting for target.network before giving the user the login screen.. what deranged mind conceived of that idea?)

Systemd can also be criticized for using way too many resources. While the developers of systemd are probably wholely unconcerned by such matters (as with every problem that doesn't affect them personally), and as a result do not optimize for resources, I believe this is more a symptom of the growing monstrous complexity.

Systemd has many optional components. What optional components are used is determined by your Linux distribution. As long as developers of third-party software do not create hard dependencies on any systemd component things will be fine for non-systemd distros; software that aims to support the BSDs will be fine. For systemd users the cancer will inevitably keep growing in size.

Let's take a moment to talk about logging. Systemd has a component for that, but it logs to binary files. "Why would you log to a binary format?" you might ask, faster indexing they tell me. Fair enough, I just want to identify the cause when an error occurs; File corruption detected at /var/log/journal/2dd.. This is a silly grievance, in a sense, I don't even really care about journald. journalctl is a piece of software, it works, it could work better. It is a querying tool or something strapped haphazardly to a pager; it should have been an interactive tool (like top) where output formats could be changed in real time and time spans and targets changed on the fly. Journald and journalctl are a bit pointless in their current form; they make the perfect point: you might think this behemoth that is systemd, for all it's parts and components and features, would contain a mechanism for ensuring that the configuration is bootable. That is a pretty nifty feature to have. No, says the German narcissist crybully: a configuration change can cause the system to fail to boot. No, says his buttbuddies: a configuration change can cause the system to shut down. Instead, have an undercooked logging tool that nobody asked for, solving a problem nobody has.

Speaking of configuration changes, at one point the systemd team decided that killing background processes (screen/tmux) on session logout was a reasonable change to defaults. I think that's pretty rad. Fuck the users.

I thought to outline more individual issues and reference bug reports, but I tired of this rather quickly. A few years ago I actively hated systemd; today I barely think of it as I use a distro with a sane init system, and only interact with it when messing with RHEL at work. RHEL is also shit. I think being shit might be a fundamental part of the Red Hat DNA.

I'd recommend reading "systemd, 10 years later: a historical and technical retrospective" if you have the interest and time.
 
  • Like
  • Winner
  • Lunacy
Reactions: ToastedButter, Administrator Flotsam, Pillar of Autism and 4 others
You must log in or register to reply here.
Back