Linux aims to provide a reliable, open-source operating system that can run on a wide variety of devices and platforms.
Linux aims to provide a reliable, open-source operating system that can run on a wide variety of devices and platforms.
I've frequently relied on Linux as my main operating system and I'm convinced it can be overwhelming. CentOS, Fedora, Arch Linux, Ubuntu, Linux Mint, Debian and many others are available. The biggest issue is that most programs are maintained by individuals who decide to stop supporting them. When they choose to discontinue something, the software gradually disappears without proper maintenance, raising questions about sustainability and funding. "It's simple to install, just use apt install junk," they say, but this overlooks the need to configure repositories correctly. Options like snapd or Flatpak exist, though they have limitations—snapd doesn't add applications to your menu, and Flatpak lacks full compatibility. A major concern is Nvidia users: Linux isn't a viable alternative. Even with Fedora, it's essentially the same as other Debian-based systems like Ubuntu, which are often less reliable. It seems everyone is creating their own solution, making things complicated. If a change is significant, it would be better to develop a unified approach using multiple package managers such as pacman, apt, dnf, and yum. A well-designed distro would simplify the process, turning what feels like chaos into a manageable experience.
I operate four Ubuntu servers in my lab alongside a Windows 10 machine and a FreeNAS setup. They're running on an old i3 processor with just 28 GB of memory. I haven't experienced any issues, even with limited RAM. The other components work fine, though I wouldn't say Ubuntu is overly heavy compared to Windows. I managed it on 768 MB of RAM without any problems. Everything else seems to be fine.
It seems you misunderstand the main idea. The key is that it's open-source and anyone can use it as needed without licensing concerns. If it doesn’t meet their requirements, they can adapt it to their own purposes.
The aim of open-source software (such as Linux) matches its title: open. This doesn't imply 'free candy,' but rather 'open access' or 'free expression.' I'd like to clarify, but Wikipedia provides a clear explanation if you're interested: https://en.wikipedia.org/wiki/Free_software
Some receive compensation through contributions or via the Linux Foundation; others simply engage in it as a pastime. When something gains traction, it often branches off and evolves under a different name. However, it remains open-source software, allowing you full freedom to modify it as you see fit. What you're likely describing is repository fragmentation—many distributions struggle with this issue. I've consistently preferred Ubuntu-based systems, though they tend to be the most problematic. This stems from the fact that most distros lack a unified central repository and depend on individuals to maintain support for unsupported software. The only community-driven repository I’m aware of is the Arch User Repository, which also requires manual compilation for many packages. Tools like flatpak and appimage have emerged to address this, though adoption hasn’t been universal.
I’m uncertain whether flatpak or appimage came first, but their aim was to provide a consistent format for downloading and running software across different distros or package versions. Progress has been made, though it’s still not fully embraced.
NVIDIA mandates a closed-source driver unrelated to Linux, while AMD avoids this due to its open-source model. Many distros refuse to include it because of compatibility, licensing, or proprietary reasons. Each distribution caters to distinct audiences: Arch appeals to advanced users seeking full control; Manjaro to beginners wanting accessible, near-edge packages; Ubuntu for businesses and cloud environments; CentOS for stable servers; Mint for newcomers needing a beginner-friendly OS.
Distros differ in package age, dependency management, out-of-box support, and more. You might be seeking a cutting-edge cloud setup with the latest features, or a more traditional system with robust security updates and ease of use—perhaps something tailored for music production with unique customizations.
People often attempt to improve upon existing solutions by forking them, building their own versions. This can lead to fragmentation, a challenge Linux has faced for years but is gradually improving. A good illustration is the debate between snapd, appimage, and flatpak—each strives for similar objectives in different ways.
Choosing a solution depends on your needs: whether you prioritize bleeding-edge features, stability, ease of deployment, or specific functionality like music production. Depending on your perspective, some distros now offer all three, though adoption varies.
Web link for further reading: https://www.ostechnix.com/linux-package-...s-flatpak/
just SSH and no graphical interface. My single testing server has operated reliably for two years without any downtime. However, when installing on Fedora you need to add the repository to install ffmpeg for YouTube, and I also have to remove Pulse Audio because it was causing issues and strange audio. For instance, MongoDB Compass isn't available on Linux, or at least I haven't been able to get it running, and the information I found is unreliable with similar problems. Some people don't grasp that I've opted for a lightweight driver rather than something heavy for servers.
One might have looked up information instead of sharing confusing comments. It would have shown that many developers and maintainers actually earn a living from their efforts. Those who aren't compensated will be replaced by others if enough people are interested, highlighting the nature of human motivation.