- cross-posted to:
- 196@lemmy.blahaj.zone
- cross-posted to:
- 196@lemmy.blahaj.zone
You must log in or register to comment.
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.
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.
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.
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 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
Oh! So close, Honey. We’re looking for vim and dark-mode. But thanks for playing.
Counterpoint it would be the year of the Linux desktop if we all agreed on
- Artix
- OpenRC
- Wayland (but different implementation)
- pulseaudio
- non-gnome gtk
- Hyprland
- Vim
- AUR
- dark mode always
I’m with you all the way, really, except that, truly, KDE plasma and dark mode are the superior choices, obviously :)
Not to mention openSUSE Tumbleweed instead of Fedora :)
And Arch Linux instead of openSUSE Tumbleweed and Fedora 😊
And NixOS instead of Arch Linux and openSUSE Tumbleweed and Fedora 😊
- openSUSE better
- yes (zig is good too)
- dinit
- yes
- yes
- Qt
- cosmic (when it’s done)
- Emacs
- flatpaks are good at their job, but I want system packages too
- dark mode is infinitely better
light mode??? 😂
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.
yall need dark mode extensions on yo browsers
