I mean it’s also socialist, with how it’s developed and distributed. Despite capitalists making use of it too. It’s one of the few things in this world the people truly own collectively.
Capitalists making use of and profiting from socialist programs and structure is a tale as old as capitalism.
Pharma as an example. Crowdsourced research, government funding with money from the people only to be bought by a capitalist corpo where they do the last 10% of the work by industrialization, jack up the price by 1000x, and take 100% of the profits and don’t even pay back their fair share in taxes, and then get a state-sponsered monopoly for an outrageous period.
In my experience, Linux folks are just happy to find each other in the wild.
Hell, I’m just happy to meet people that are Linux-curious lol.
It’s mostly online that the distro wars are fought.
It’s the same with leftists in my experience. The fighting is worst online
I’ve never met a linux enthusiast or even a user IRL. So at this point if I ever do, they will achieve best friend status off of that alone.
So strange that an operating system has that affect on me
You never knowingly met a Linux user. Statistically speaking, you probably have.
The issue is that OS-preference is not very common as a small talk topic. This is why you should name drop your fav distro in every conversation.
2025 would be the year of Linux, if we could finally agree, that:
- Fedora,
- rust,
- systemd,
- wayland,
- pipewire,
- gtk,
- Gnome,
- nano,
- flatpak, and
- light mode
is the perfect stack of technology and configuration and that we do not need anything else. But no, you guys just had to disagree, and here we are …
I’m with you all the way, really, except that, truly, KDE plasma and dark mode are the superior choices, obviously :)
Better UI consistency. It’s always really annoying when you have your nice dark theme and a bright white page pops out of nowhere and fry your eyes.
For ease on the eye, keep everything black on white, and turn down screen brightness if the environment is dark.
Surprised how, of all the people who took the bait, not a single one of them complained about systemd.
My beard isn’t long enough to have an opinion about systemd. All I know is all my homies hate systemd for some reason.
A lot of complaints I’ve seen is that it’s bloated - it’s not only a system manager but also has a DNS relay, network manager, container manager, and so on.
That said, codifying service startup and managing them with cgroups is IMO MUCH better than init scripts that think running killall apache is a good way to stop a service.
I beg to slightly differ, but it’s a good take overall:
- Aeon Desktop or Fedora Silverblue, any sane immutable system, really
- Zig + Rust + Scheme / Clojure
- systemd,
- wayland,
- pipewire,
- gtk,
- Gnome,
- nano / gedit / whatever y’all are using instead of glorious Emacs
- flatpak,
- distrobox
- light mode
Linux Developers: “Here’s the thing, you’re not going to force all of us to learn Rust.”
This meme couldn’t be any more fucking accurate.
Lol. If Rust fans want a Rust kernel, no one is stopping them from building one.
It’s hard to overcome the Hurd problem though. Although it would be fascinating to see how it would diverge on the design of the Linux kernel. How much can you still act like Linux while not being Linux? Or would it just be a direct algorithmic translation, basically doing the same processes under the hood with the same architecture? I’m sure there’s more than a few things Linux is doing in C that the Rust compiler would frown upon.
Main issue is drivers. One of the best places to take advantage of rust’s memory safety is in hardware drivers, and those would be hard to share between separate kernels.
That entire talk, and the complaint that Ts’o responded to was that to continue with rust, there needs to be some responsibility from the guys working on the underlying C bindings to not break downstream dependencies if they refactor code.
The answer from some of the Kernel developers, and vocally by Ts’o was: lol no fuck you and your toy language.
Yeah. The idea of an automated C to Rust replacement of the Linux kernel is fascinating. As you say, there’s probably stuff in the Kernel that Rust’s compiler won’t allow.
I imagine it wouldn’t work at all, out of the box, but it might reduce the cost curve enough to make a dedicated team of very clever engineers able to cross the last mile, given time.
As cynical as I am of both Rust and AI generated code, it honestly feels like trying an automated conversion might be less of a long shot than expecting the existing Linux kernel developers to switch to Rust.
And I’m sure a few would kick in some thought cycles if a promising Kernel clone could be generated. These are certainly interesting times.
They’re also similar in that if you tell them you use Linux but like Canonical and/or Lennart Poettering they’ll yell at you and call you all sorts of names but if you tell them you’re a Windows user they’ll leave you alone
