There is in this case, and why Linus did accept the patch in the end. Previous cases less so though which is why Linus is so pissed at this one.

The reason for this new feature is to help fix data loss on users systems - which is a fine line between a bug and a new feature really. There is precedent for this type on thing in RC releases from other filesystems as well. So the issue in this instance is a lot less black and white.

That doesn’t excuse previous behaviour though.

Only 40%? Would have thought it would be much higher. Don’t more projects generally fail then that without being in a bubble?

There is not really one best distro out there - or else there would only be one distro. But for someone new you will find basically any mainstream/popular distro good enough for your usecase. The best one for you will come down to personal preference and will likely - at least at the start - be centered on which desktop environment you like the most. KDE will probably feel more like Windows. Though gnome I think tends to be the default on most distros. You will find popular distros have multiple flavors with various desktop environments as well. Your best bet is to download a few and put them on a usb and try them out before installing. That will give you a better idea of what you want.Or just pick one and go for it if you don’t care that much - it will probably be good enough.

I said editor, not an OS that lacks a decent editor :)

What editor is more feature-rich then vim? Out the box it is lacking some sane config but it is one of the more powerful and flexible editors out there - more then a rival for any modern IDE.

Vims defaults are quite crap overall. It is why everyone needs 100s of lines of configs and many plugins to turn it into something decent. Well worth the setup but it could go a long way to making things nicer to use out the box.

Nobody sane uses vim as an IDE

Huh? Many people do this. With the right plugins and config it is just as capable as any IDE.

The problem is ides inlining only part of the error and generally skip all the helpful text on how to fix the error.

From what I can tell xbps-src are just the source packages to the main repos in Void. That is not what AUR is. We have access to the main repo sources in Arch just like Void. The main thing about AUR is anyone can contribute without any gated approvals. That is the big difference between the main source repos of either distro and AUR. Unless I have misunderstood what xbps is.

but looking at templates they can actually understand its kinda simple script and get the idea of how it works

Same exact idea with PKGBUILDs. No benefit to Void here. The way Void does things will not change people looking at or understanding the packages they install. You have the same optitunities on both systems for looking at the source of packages. So that argument for Void is void :)

Also void has runit so this mean u have to get more simple programs to run system like seatd dbus and etc.

Not really a good argument either. Systemd and runit are different but that doesn’t make runit better in terms of learning anything. If you want to learn how most Linux systems boot and operate you need to learn systemd as that is what the vast majority of distros use. Learning runit instead only means you are learning a niche way of booting a tiny fraction of systems.

Neither of these arguments are a very strong case for Void over arch.

XBPS-SRC does not look like an alternative to AUR at all. It looks like Voids alternative to https://gitlab.archlinux.org/archlinux/packaging/packages - where Arch maintains all its packages. Nor is comparing the number of packages in AUR to Void main repos a good idea - Arch has its own main repos that are a better equivalent. The Void templates do not look dissimilar form what a PKGBUILD file is either and you can do the same things with writing your own PKGBUILD or pulling them from repos if you really want to. I don’t see how void is any better then Arch in anything you have described here. IMO it just looks like it does more of the same things with a bit difference in syntax/commands you run. Nothing you have said here is really a solid argument for using Void or Arch at all.

The AUR is not even that great. I think most people seem to get confused between what is in the AUR and the main packages since they just use tools like yay that install from both. But most people only use a couple of packages from the AUR - it is the package selection in the main repos which is what is so nice about Arch. The AUR is just nice for more niche things that have not made it into the main repos yet.

I hope u don’t use AUR blindly and just do yay -S something without looking what pkgbuild is doing, it might be dangerous not knowing what program can do and what script that is downloading it too right?

Same goes for Void? Most people wont read the source of third party packages they install. No matter what distro they are on. AUR tooling does try to help with this but most people ignore it. Same will go for Void. It is not a distro problem - just a humans are lazy problem. Plus even if people did read them there is only a small subset of people that actually understand them enough to spot obviously malicious packages - though that can spot hidden malicious packages are vastly smaller.

252 of that 592 used memory is buffers/cache, not application memory. That is used by the kernel for kernel buffers and the filesystem cache - IE files read by something at some point. The kernel keeps them in memory in case they are needed again to speed up file reads. You can effectively ignore these vales as they will always grow to fill your ram and will be evicted when programs require memory and there is not enough free.

These tools are not lieing to you, just telling you something other then what you are reading into them. Tracking and reporting on what is using memory is a complex topic and here used is just what is physically allocate. It doesn’t mean much over all as it always tends to be full of your system has been running for a decent amount of time. Available is typically the more useful one to look at as it is an estimate about how much the kernel can reclaim now if an application request it without needing to swap things out.

Can you share the output of free? There are multiple values to read from that.

None of that describes why a beginner would not want to use a immutable distro. It only describes why it is not a good idea if you want to learn how traditional linux distros work. Not all beginners want to learn or care about how linux works under the hood and immutable distros can be a good fit for them. They might not be right for OP, but you have not describe any reason why any beginner should avoid them.

I saw some people using Arch to learn the inside out of Linux, but I’m afraid It could be to challenging.

It will be challenging but IMO give it a shot if you think it is something you might want to do. No harm in trying really. If you mess it up or find it too hard or whatever you can always install something else afterwards. It is not like you are stuck with your first choice forever. The only thing you will lose is a bit of time and will gain a better understanding of things even if you cannot make it fully work.

I don’t agree that arch is not a beginner distro - it is a DIY distro that requires a lot of reading and willingness to learn and understand things. The arch wiki is an excellent resource for anyone (on any distro IMO) and well worth reading. If you are OK with that work then it makes a fine distro for anyone, beginner or not. It is not a distro for many people - again does not matter if they are a beginner or not. It is for people with a particular mindset. One that you might change over time or as you grow and learn more overall.

No harm either if you decide it is not for you. Play around with a few distros and try to find which one works best for you. There is really no one best distro. Just a lot of different things that appeal to different people and the only real way to find out which you like is to try them out.

But why won’t anyone think of the AI shareholders…

That is the type of thinking that causes a massive amount of CVEs in those languages.

Hey, the design specs never said the program shouldn’t blast out and air raid siren at full volumn every time the user clicks a button. Cannot be a bug, must be user error.

The company you work for will likely not like that. Needs a special case license to be drawn up would probably need to involve lawyers and cost far more then is worth the hassle. Vastly easier just to give it a MIT license.

If you want to be safe backup anything you care about before hand. Assume that you might end up needing to wipe the system and reinstall everything. Encrypting the Linux partitions should not affect windows but there are so many other steps that could go wrong when partitioning and installing a system it is better to backup everything you care about just incase.

There is good reason to think it is not just rust.