It all depends on what you actually want to do.

I have a computer connected to the TV with Chimera installed because that’s SteamOS 3 with emulators preconfigured and is completely couch + controller friendly.

My laptop has Fedora because it’s up to date, but everything is tested before release, and all upgrade paths are automated unlike Arch which burnt me in the past with breaking changes.

On my Pi’s I have Diet Pi, which is Debian but has images for each of the different ARM boards and has a bunch of scripts for setting up print servers, Home Assistant, etc. I want Debian for it’s slow unchanging nature there.

On my desktop, less so.

But underneath they are all Linux, and they all behave in very similar ways, it’s all about the initial setup.

Stable has nothing to do with outdated packages.

That’s a personal decision by a distro.

Fedora is a stable distro because generally the packages stay on the same major version throughout the version, however they have a list of exceptions for certain applications that should be updated for security or perhaps they don’t follow a major/minor/bugfix release and it’s bad practice to hack together your own versions.

Fedora rebases it’s packages every 6 months, so it’s never left far behind.

That doesn’t make it “trash”.

Most people are not accessing the internet via a Chromebook.

I only had bad experiences with an XPS, then I found out that the Linux model was a cut down version so that Dell didnt have to support the fingerprint reader and other gadgets.

Lenovo at the time were working with Fedora to get all their fingerprint drivers upstreamed so the choice seemed obvious.

AMD T14 Gen 2, and it’s still great.

deleted by creator

What do you mean I can’t install Windows on my new MacBook??? I thought it was only Linux that you had to think about what hardware you were purchasing before whining about incompatibilities.

And also running through FutureCoder

https://futurecoder.io/

Gradle, with it’s transitive dependency modifications is a huge pain in this area.

It used to be that if a library ended up having a flaw then it would be flagged and we would get the dependency updated. These days security block the “security risk” and you have to replace your dependencies dependency. Fingers crossed you can get it to actually test all the code paths.

If an second level project gets a flaw, and it’s used indirectly then we should really look at getting the import updated so that we know it works. If that import is abandoned then we should not be updating that second level dependency, either adopt and fix the first level dependency or look at an alternative.

If I remember correctly, from a friend who was trying to do something on a Synology, there was something screwy about those devices.

Images that worked fine on a PC or a Pi just didn’t on the Synology. It’s been years so I don’t remember what, but don’t take those systems as a good example of Docker.

Yep, completely agree. That was essentially the last line of my comment.

I also wish that journald had a spec for its database, or standardised on something like Sqlite which could be interrogated with generic tooling.

While I agree that sometimes Uber projects happen, for efficiency or security reasons, I don’t think that Mesa is a good example as they have a scope (implement the OpenGL/Vulkan API) and stick to it.

Systemd is already confusing because of it referencing two different projects, and the overarching systemd projects scope just increases on a regular basis without what appears to external observers as a plan.

This will probably lead to vocal outrage because it’s Systemd rather than an alternative project coming up with the solution.

Sudo has long known to have dangerous weaknesses, but it’s generally been accepted since sudo solves a bunch of other problems. If we can fix the problems sudo has, then that’s a good thing. Would be nicer if we could split up some of these projects though to stop uber projects.

My point is not that you can’t

I’d just like to remind the passing reader that creating an open source project does not entitle you to do whatever you want and tell people to “make their own thing” if they don’t like it.

It was literally what you said, even if you didn’t mean it to be. And I don’t think that being a dictator for your project is necessarily “toxic”, I have projects that take contributions and I work on others that do not. Bikeshedding, and horrible politics, are both real things and sometimes for your own sanity, not engaging is the only option because community is not the reason I work on some tasks.

Some projects are just natural candles to moths who will talk to the projects like this:

https://www.reddit.com/r/github/comments/1at9br4/i_am_new_to_github_and_i_have_lots_to_say/

Fuck that.

Of course I’m not entitled to community contributions. Just as a user, you are not entitled to me fixing your big reports.

That doesn’t stop it being an open source project, and a lot of developers don’t want to deal with a needy community for their own mental health. It was an itch that they scratched.

Hopefully this is satire.

If I create an open source project I can run it however I want. I do not have to create a board to manage it, there are plenty that have a single developer doing all the work, like VLC, and like Sqlite they may or may not even accept PRs. It doesn’t stop it being open source.

If I do create a foundation, I can fill it with whoever I see fit. If there is a board, then generally they have the last say but there are plenty of projects, like Python used to be, where there might be a board but the founder remains the benevolent dictator for life and will stop them doing stupid things that distracts from the core project. Look at Linux, the project is mostly self maintained but Linus will gatekeep anything that doesn’t meet his definition of success.

If my rules for my project is that all board members have to be a furry, then that’s my right, and maybe the board of furries will vote to overturn that. Or maybe they won’t. But you can’t tell me how to run my project, this isn’t a democracy.

However since no one tests it I’ve found them to be really buggy. Hence why I suggested just using the web app.

What were you trying to screen share with?

Most of the apps people are using are Electron, which has supported Wayland and the pipewire screensharing for nearly 4 years. However since Chrome/Chromium doesn’t enable Wayland by default, Electron won’t. Which also means that no one tests it in their apps.

I’ve had such success just ignoring the apps and using the web client since that’s up to date and doesn’t require the app builders to enable features.

At least under Fedora.

Nvidia didn’t want to play nicely and give standard APIs.

Their work around was other extensions that don’t actually do what’s needed, but sort of works in some scenarios.

All the GPUs I’ve used work fine, it’s a Nvidia throwing it’s toys out the pram situation which should hopefully get resolved as they open source the high level drivers and so the correct APIs can be implemented.

Like?

If there is something missing, add it either as an issue or a PR in the project.

https://github.com/mpsq/arewewaylandyet

It would help your case when saying that it’s not ready. It might also inspire people to fix it if they see something that is missing.