a big neurodivergent pile of vegetable matter // 29 // sf bay area
I’d argue Fedora Atomic does the job with even less fuss for a larger number of people. NixOS is great if you want/need to tinker, but Fedora Atomic is just giddy up and go as long as you don’t require any specialized programs or drivers.
I say this as someone who currently uses NixOS on both of my computers.
It’s just a cute little comic strip that conveys a fun message.
It’s basically focused on establishing good community-centered governance, cleaning up the codebase, standardizing workflows (reconciling disparate parts of nix), and (I think?) eventually reimplementing the whole thing in Rust instead of C++.
Aux is only keeping the code on GitHub temporarily because money is tight and there are very few options for a soft fork of a repo as huge and active as nixpkgs. Plus, they want ease of accessibility for devs considering it’s a very new project.
Long term plans are to move off of GitHub. I’m pretty sure some people are talking to Codeberg to see how feasible it would be to move there in the future.
Okay? OpenSUSE Leap is a point release by and for companies. While Fedora isn’t necessarily a server distro, it IS a point release designed with enterprise use in mind.
If we look at both of their strictly enterprise counterparts, I’ve never heard of any complaints about SUSE and any complaints with RHEL I’ve heard are with source availability. Neither of them have the mega amounts of bad publicity of Canonical.
The lesson is to use a Community distro, not a Corporate distro.
Okay, but you don’t see these kinds of complaints with Fedora or SUSE. While I don’t necessarily disagree with your core point (community is better), this doesn’t seem like an issue with corporations so much as an issue strictly with Canonical.
Immutability, mainly.
These entities all have similar names and share similar origins, having been started by the founders of Open Collective and incubated in the Open Collective ecosystem, but are independent nonprofits with their own budget, accounts, staff, board of directors, and mission. They each have a separate commercial relationship with Open Collective. [emphasis not mine]
Open Collective, Inc. seemingly has nothing to do with OCF shutting down and neither entity has claimed anything to the contrary.
This post also clarifies the differences between the entities that make up the Open Collective family and what this dissolution means.
Though I have yet to try Guix, I think I’d move over to it if they adopted something similar to flake support. The idea that it uses a non-arbitrary language for declaration is very appealing to me. Do you know if it’s simple enough to get non-free kernels, though?
Plasma and GNOME are two completely different projects made by completely different organizations made on completely different technologies with completely different philosophies. That would be like proposing that McDonald’s and Wendy’s merge.
Yes, open source development isn’t necessarily as efficient and doesn’t lend itself to as nice of UX/UI/etc, but that’s not the point. The point is the freedom. Do I wish, as a GNOME user, that GNOME had certain features that Plasma does? Yeah, but part of the reason I like GNOME is that they’re so stringent about what makes it into the DE that it makes for an infinitely more polished experience than Plasma. You can definitely approximate the GNOME workflow on Plasma well enough, and that’s the great thing about Plasma: you can do almost anything you want with it.
You’re not the first person to propose that open source projects merge, and you certainly won’t be the last, but freedom also implies that you work on what you want to, so let people work on what they want to!
BTW, there are certainly more DEs than just GNOME and Plasma. Maybe try Budgie! It’s like the default workflow of Plasma mixed with the simplicity of GNOME.
Endeavour has plenty of “beginner” tools, including a kernel manager (literally called A Kernel Manager) and a friendly GUI Welcome app that helps you update your system and your mirrors.
Literally one of the Plasma devs showed up in the thread and seemed very annoyed.
In short, the maintainers have made questionable decisions over the years, and the Arch Linux packages are held back by two weeks on Manjaro for… basically no reason.
If you want an out-of-the-box solution to Arch Linux, just use EndeavourOS.
Element is starting to look really really nasty in all of this. It’s disconcerting to me.
The app itself has to support it, and even then those options can be hit or miss.
They have, but it’s more of a container development kind of thing.
Tumbleweed isn’t immutable… Aeon (previously MicroOS Desktop) is.
(This is going to be grossly oversimplified and possibly minorly inaccurate, but) Flatpaks are built against and run using shared runtimes, so if two Flatpaks share the same basic dependencies (and those dependencies are included in the most common runtimes, which they usually are), you only have to download the shared runtime once. Every Flatpak built on the same runtime will share the one runtime. The way you described it is a common misconception.
Now if the packager manually bundles less common dependencies into the app itself, yes, that would have to be individually updated, but that’s theoretically more of an edge case.
Only iPhone I ever had and I loved that thing to bits.