No. We’re all waiting for this guy to activate it so we can get to work.

systemd, as a service manager, is decent. Not necessarily a huge improvement for most use cases.

systemd, the feature creep that decides to pull every single possible use case into itself to manage everything in one place, with qwirks because making a “generic, do everything” piece of software is not a good idea, is not that great.

systemd, the group of tools that decided to manage everything by rewriting everything from scratch and suffering from the same issue that were fixed decades ago, just because “we can do better” while changing all well known interfaces and causing a schism with either double workload or dropping support for half the landscape from other software developer is really stupid.

If half the energy that got spent in the “systemd” ecosystem was spent in existing projects and solutions that already addressed these same issues, it’s likely we’d be in a far better place. Alas, it’s a new ecosystem, so we spend a lot of energy getting to the same point we were before. And it’s likely that when we get close to that, something new will show up and start the cycle again.

Native package manager > Native binaries > AppImage > Flatpak.

Yes, snap isn’t even on the scale.

They’re planning on making a version where everything is a snap. Performance and usability may come later, who knows.

“Stalled I/O” has entered the process list :D

Someone made that, sort of. Unfortunately, the privacy nightmare is slightly reduced compared to the original one.

https://github.com/openrecall/openrecall

The good old lying approach, I see.

I use a mouse btw.

For a lot of project “compiling yourself”, while obviously more involved than running some magic install command, is really not that tedious. Good projects have decent documentation in that regard and usually streamline everything down to a few things to configure and be done with it.

What’s aggravating is projects that explicitly go out of their way to make building them difficult, removing existing documentation and helper tools and replacing them with “use whatever we decided to use”. I hate these.

Fair. Also, flatpak does not try to break everything by default, which is a plus.

I like the “encryption, but we have the keys” approach. Makes it very secure, especially since MS never had any security breach or leak, ever.

HTTPS isn’t only about encryption; it’s about talking to the right servers.

.txz, I’m too lazy to type the full name

I’m trying a new approach. Since I won’t touch anything beyond W10, and W10 is getting officially phased out, I just informed people that I won’t provide tech support for W11 and beyond.

Not at all. I’m arguing that often, the issues, and fixes, are not distribution-dependant. Which is a good thing; it means we can go to arch forum and find fixes that can be applied in other distros most of the time, for example.

But people keep pitting them against each other like they’re some form of evolved lifeforms that necessarily have to erase others, when a lot of the issues are just generic software issues.

And, since this is already a justification post I’ll take the lead and note that it does not mean that there is no distribution-specific issues. Of course there are. The point is that most software issue in distribution X will have the same cause and fix in distribution Y, and often have nothing to do with either specific distributions.

People keep arguing about this or that distro.

Linux distributions are just a collection of software, initial settings, and sometimes online repository.

“New device detected: mouse. Please wait…”

But the mouse is already working dude.

Heck, I have errors in windows log that are just “sure, let’s move on”.

It’s ok, they just started the “security first” initiative, we’re all saved.

There is no software solution that protects from a crowbar, you have to go to the hardware side.