u/subdiff

It should also be possible to delete old snapshots when the space gets low automatically.

I recently tried Slint. The C++ API seems to be not as important to the devs as the Rust API. I wouldn't recommend it right now.

In any case it's probably: https://askubuntu.com/a/829996

Are you using Discord through the browser? If yes, which browser?

I have only used pandas until now. pandas uses NumPy internally. Has DataFrame a similar relation to an underlying project/library?

How can it be compared to https://github.com/dpilger26/NumCpp?

That's nice to hear. Newer kernels sometimes come with better support for certain hardware devices.

But watch your system some more. There might be other problems introduced with more recent kernel versions (sleep not working etc).

Yes, test it out and see if bluetooth works better. You can always go back to the LTS version by selecting it in the Grub advanced menu options at boot.

Maybe try a newer kernel then. You can install and uninstall kernels from Manjaro settings.

Looks like the update wasn't complete. Try to chroot with a Manjaro live USB: https://forum.manjaro.org/t/how-do-i-chroot-into-my-system-and-update-my-kernel/129729

Also create backups while at it.

Nextcloud aio is good

Battery life is usually good. But you must try yourself with your particular model.

Make sure tlp is installed.

You can do that but it's not unlikely your system will be broken in some subtle ways as these are many packages to replace. Start with something like the plasma-meta package and then see what else you need and what can be removed afterwards. And make a backup of important data before that.

You're on stable branch, right? Updates should come in slower there, I'm pretty certain not at 0.25gb/day.

Bluetooth not working is normally a kernel/hardware problem. What kernel are you running with what hardware?

There is currently no roadmap, but I'll push for switching to 6.1 being pushed to stable branch soonish.

But you were earlier comparing with the CrowdStrike Linux incident, which affected only servers as far as I know. And that didn't have a noticeable impact albeit the Linux marketshare on servers is bigger.

On the other side the CrowdStrike on Windows incident also affected Windows thin clients and servers, not only workstations.

Due to the marketshare of Windows, the tiny subset is still large enough to have impact. Was Linux the one with this marketshare, the chance for such a fuckup would rise as well.

Linux marketshare is bigger.

I know about it. But how many websites you couldn't visit because of it? And that's while most web servers are running Linux. How many businesses had problems in a way that happened with the fatal ClowdStrike bug on Windows?

I'm not saying the problem due to malpractice is not possible on Linux, because of course it is. I'm saying it's neither a problem on average nor in any meaningful capacity. And that's because of a different culture in how Linux systems are used and maintained, especially in terms of security (while admitting that of course no system is perfect).

Yes, and I would argue that such a design has been chosen and could be sold to customers, because by extension the Windows ecosystem - and its users - follow a fundamentally insecure strategy how systems should be secured. And yes, while surely not everything is perfect, we don't have this problem in the Linux ecosystem.

This has been brought up to them before and they refused to give an answer.

Got a link?

We're discussing the topic internally. Tbh in my opinion there are not many good arguments for us shipping the gimped version on normal ISOs. I hope we'll soon find a compromise to ship the normal Mesa version again.

Right now they are getting automatically renewed with certbot. But I want to revisit our infrastructure overall in the future, maybe I'm gonna look into Caddy more closely then. Haven't used it until now.

I know, topics about Manjaro in /r/archlinux are often not fancied, but as the author of the article I'm interested in what Arch Linux users and developers think about the article and especially a potential immutable version of Manjaro/Arch Linux.

customers have responsibility too to test before roll-out

They couldn't. It was pushed directly to their machines. The fundamental issue is the idea that inherent Windows security problems can be mitigated by trusting another "security software vendor" in the critical path. Instead you just create one more weak spot.

The article linked here discusses this.