Fairly sure that Matt Mullenweg has already completely undermined Wordpress.org’s trust and reliability.

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.

I never thought shaking the bed would cause adhesion issues 🤔 always thought it was far more the head crashing/clipping or scraping the surface of the part while printing.

Restrictive tech never works when you apply it from the start. You need to capture the market first before you can start to apply that. And that is the road Bamboo labs looks to be heading down. It is the classic playbook:

1. have some true disruptive innovation in some product that people will actually want to use your products for ✅
2. mass market your product and get loads of people singing parse about how innovate it is ✅
3. slowly start to lock down your product, typically behind the guise of safety and security ✅
4. start to squeeze your customers for as much money as you can with DRM or subscriptions You wont succeed if you skip straight to step 4. But Bamboo have been slowly working their way up to it. It might take a few more years but I can see them eventually wanting DRM filament.

One step closer to DRM filament spools. Just like the overpriced ink cartridges of 2d printers. The safety and security arguments are always bullshit. This is only about control over what you can do. No other printer has ever had an issue with safety or security with vastly more open designs.

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…

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.

But there are more numbers between 0 and 1 then there are whole numbers. So are the countable many angles or uncountably many?

‘I never thought leopards would eat MY face,’ sobs woman who voted for the Leopards Eating People’s Faces Party. - Adrian Bott

Any service you use passkeys with instead of passwords won’t put you in another leaked password database. The public key just needs to be invalidated and you can move on with your life.

Does it though? Is there anything wrong with your public key being, um public? All they can do with it is verify who you are, (or technically encrypt things that only you can read - not that pass keys are used in this way?).

Passwords can be secure when the end user picks a strong one. But that is the biggest problem with them, the end user. They don’t pick good passwords and decades have shown us the general public are bad at passwords.

Passkeys are not biometrics. They are much simpler. In a very simple way you can think of them as a secure long random password that is stored on you device, generated per device, and not sent over the wire to the other side (so more like public/private key cryptography I believe).

The passkey on your device can be stored in an encrypted vault or even secure hardware that requires a pin/password or key to unlock.

They are not getting rid of multifactor codes and can be used with them. But by protecting them locally you can still have 2 factors to access them - the hardware/vault that contains them and the pin/password/biometric that unlocks the vault. And that is in addition to server side multifactor systems.

But even without all that you still gain massive benefits over passwords as it stops cross site comprises when one sites gets their password database leaked. Or brute forcing access to systems by guessing weak passwords that most people use.

You should have a live USB of the distro you want to use and ensure you have backups of all the data you care about. Then the easiest/quickest/least error prone way is to just wipe the whole drive and reinstall the distro from the live USB. They typically have an option to wipe and install things from an empty drive. Then just restore your data from your backups.

You could also, after creating backups, from a live USB environment delete the windows partitions and resize the linux ones - being careful not to delete the EFI partition as that is where the boot loader lives. You can optionally delete the windows boot loader from the EFI partition as well. If done right you should still be able to boot into your linux system afterwards though when missing with partitions like this, especially when you don’t know what you are doing, it can be easy to break the boot systems. These can be fixed from a live environment and there are many guides out there on how to do that.

You can always just reinstall the system again if you mess things up and cannot figure out how to fix them - so always prep for that case by backing up everything you care about first.

Some people might dismiss Rust as being “unelegant” or “ugly”, but the verbosity actually serves a good purpose and is immensely helpful for building large-scale applications:

Here rust is trying to be unambiguous by forcing you to write just enough context when needed. It is not unnecessarily verbose at all and is not trying to be absolutely explicit about everything. When there could be more ambiguity, rust errs on the side of being more explicit which increases the verbosity. But when it is less ambiguous then it favors being less explicit. Hence why you can omit types and lifetimes in most situations but require them when it is not obvious what they should be.

Battery self discharge is measured in days at worst, more typically weeks or months. It should not be dropping 5% over the course of an hour or so even if the device is a bit warm. Plus having it plugged in should start charging again once the battery starts dropping too low.

You shouldn’t see the battery drop if it is not using the battery, which is what pass through would suggest.