Idk, it's a hobby. There's no problem with new distros. If they're good, they take off, if not, it's going to be a niche project. No issue at all.
this post was submitted on 10 Apr 2025
535 points (84.3% liked)
linuxmemes
24470 readers
539 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. 🇬🇧 Language/язык/Sprache
- This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
I'd say actually a bit of the opposite. Generally speaking we don't need a new package manager or init system, and better hardware support is almost entirely a kernel concern (one might make an argument that the loose bits of key management and tpm2 tools and authentication agents could be better integrated for "Windows Hello" type function I suppose, but I doubt that's what the meme had in mind.
Not really needing to reinvent the wheel on those, we got a variety of wheels, sometimes serving different sensibilities, sometimes any difference in capability went away long ago (rpm/dnf v. deb/apt).
The best motivation I can think of at this point is to make specialty distribution that is 'canned' toward a specific use case. Even then it's probably best to be an existing distribution under the covers. I think Proxmox is a good example, it's just Debian but installer made to just do Proxmox. You want to do automated installation? Just use Debian and then add Proxmox (the official recommendation), because they have no particular insight on automated deployment, so why not just defer to an existing facility?
The biggest conceptual change in packaging has been "waste as much disk as you like duplicating dependencies to avoid conflicting dependencies", maybe with "use namespace and cgroup isolation to better control app interactions" and we have snap, flatpak, appimage, and nix very well covering the gamut for that concept.
For init, we have the easy to modify sysv init, or the more capable but more inscrutable systemd. I don't see a whole lot of opportunity between those two sorts of options already.
It's usually easier to criticize something than to go through the effort of understanding it. Posts like the OP are an example of that.
... And ironically, your post is doing the same thing here with software packaging:
The biggest conceptual change in packaging has been “waste as much disk as you like duplicating dependencies to avoid conflicting dependencies”,
Nobody is perfect, so it's important to keep an open mind about things, especially when one don't understand them, and especially² when one thinks they understand them as it's always possible to be wrong (unless they don't care about going through life as an ignorant asshole. Plenty of people thrive like that.)
I understand it fine, and it's not just a packaging phenomonon, all sorts of software developers have stopped trying to have consensus on platform and instead 'just ship the box'. 99% of the time a python application will demand at least virtualenv. Golang, well, you are just going to staticly build (at least LTO means less unrelated stuff comes along for the ride). Of course docker style packaging is bring the whole distro. I'll give credit to snap and flatpak that at least allow packaging to have external dependency packages to mitigate it somewhat.
i like novel implementations of these things, it's the reason why linux as it is today is so good, people were willing to try novel methods of package management, and the repo worked great.
Choose a distro by the default wallpaper.
In that case uwuntu for life.
By logo openSUSE ftw
All the different distros are all about the vibe and not a lot else. The Linux kernel remains pretty much the same and we just choose different window dressings.
I suppose we could role it all back to Debian Stable and Slackware I guess. Do we need a "Distro Thanos?" Besides, without all those different distros, how you gonna surf?
So don't harsh the vibes man.
< Do we need a Distro Thanos? > Ubuntu has enough snaps for all the distros!
load more comments
(5 replies)
Sorry, the best I can do is busybox as init.
Hardware support is not really the province of distro, to me. Which makes them even more ridiculous.
Or a new based DE, like with new libs and frameworks for making ui
At least own the libs
Make your own framework just to own the libs.
Owning libs in this economy? You'll have to settle for renting a few.
No need to make a new distro, just package it into NixOS
Just a reminder that nix packages works on most any distro, and then they work like other universal packages, but without the sandboxing
NixOS is just when you take this to the logical conclusion and have every part of the distro packaged in Nix, including configuring your OS, and optionally your users configuration files as well.
Good point
Does my distro qualify for this? I already implemented my own package manager and init system in Rust, and the only thing to do is to port build scripts from Arch to my format and make an ISO.
average yiffos distro experience really.
view more: next ›