M. Orange

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 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.

Last I heard, which was admittedly a long time ago, Pale Moon was dangerously out of date with respect to security and web standards and not much more than a meme. I feel like I remember a significant change in leadership relatively recently, but has Pale Moon actually become a viable alternative?

Beyond that, WebKit is still a thing. Ladybird is too though it’s still quite a ways from primetime.

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?

Most available “landlines” nowadays are just VoIP anyway tho. It’s why my dad got into ham radio.

Is “forced labor” any different from slavery?

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.

My interests are being gay and TV shows about middle aged women.

I tried it, but it was way too full of cryptobros. I felt like I didn’t fit in.

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.

The app itself has to support it, and even then those options can be hit or miss.

Well, she’s the former CTO.

They have, but it’s more of a container development kind of thing.

It’s important for the same reason that UX research is a pretty important field nowadays: you wanna make your software/platform/whatever as easy and pleasant to use as possible.

Alternatively, Epic lacks a value proposition. Having games spread across multiple platforms is inconvenient. Most consumers value convenience, so they’re going to stick with the most convenient (read: the most dominant) option unless they have some reason not to. For example, as messy and crappy as GOG’s storefront is, they’ve managed to differentiate themselves from Steam first by focusing on making old games playable and then focusing on a DRM-free and more curated catalog. What does Epic offer other than doing the same things Steam does but less well and in a different app?

It reads to me like they’re saying that they feel like they might be attacked by Meta employees.

That said, it’s uh… quite a choice to have made to say that.

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.