Elderly people in my family use Ubuntu (LTS) for over a decade. In one particular case, all LTS updates are performed remotely, without issues.

That’s no 20 meter wide display.

Calibre is a Java application and available as a flatpak package. Maybe check how they do it?

The article is not about which filesystem to use or not, but about the size and contents of the patches submitted in relation to bcachefs. It seems that the submitted changes which should have been just fixes also contain new functionality. Though it is very nice to see how active and enthusiastic the development of bcachefs is, mixing fixes with new functionality is hard to review and dangerous as it can introduce additional issues. Again, while I appreciate Kents work, I understand Linus’ concerns.

The sentiment is similar to climate change deniers.

I don’t think that the survival of humankind potentially depends on the adoption speed of Wayland. If anything ever breaks, it will affect only a few individuals which can then still change course.

There are a lot of people using hardware from the last decade. I would even dare to assume that most Linux desktop users do, because that’s how you still can get the most out of old hardware.

I have an old tower which I sometimes use for light gaming. It runs X11 because Wayland had some issues on this specific machine. I don’t remember which and don’t really care to investigate unless it becomes necessary. Until then I’m just happy when I have a little time to use it. And that works perfectly for my needs. For now

I don’t think it’s a revolt. Why would they put effort into changing something which works for them with the risk of breaking things? They also wrote “knowingly” which probably means that they won’t have an issue with a switch if their distro manages to make a seamless transition.

Some people just want to get their stuff done, without diving into technical details. And as long as that works for them, they won’t actively change anything.

Upvoted because DRG was mentioned.

Thank you for acknowledging the positive development. It’s so nice to see some appreciation for the effort put into solving our issues. I’m so tired of all the complaints and outrage about this or that solution, be it flatpak, appimage, snap or whatever.

Not all Lemmy instances allow downvoting. So they might not introduce friction, but they remove the (maybe un-considered) negative reaction.

Thanks for the pointer. But since Proxmox supports both KVM and LXC virtualization, wouldn’t that make it both type 1 and type 2?

I don’t think that that’s true. At least not more than for any other community maintained packages.

There also seem to be oxidation problems during the production.

Their latest album was released in 2023. They released ~9 albums since the 80s, so they should not lack material.

That unsophisticated attacks can affect critical infrastructure is worrisome.

I consider myself a newbee.

Can someone please point out some specific licenses and projects which disallow this kind of action?

Thanks, I did not know about PyXDG. That was the type of thing I was asking about.

I do. But you might have misunderstood my question. I was not asking for assistance. I was just curious if there are libraries available which allow easy adoption of the XDG specification. I imagine that such abstractions would be useful for multi-platform software and generally to lower the bar for adoption.

Are there abstractions available around the XDG specifications to resolve the proper paths?

I had a similar issue and had to reboot without a battery first, so the previous one was “forgotten”. It seems like the battery control is a completely separate circuit which in some cases needs to be be reset (if you have such options) or depleted so new batteries are recognized. Maybe search for such instructions for your specific laptop brand and model. HTH