Off the top of my head the compiler is slow because:

1. With C you can compile every file in parallel, in Rust compilation of a single crate is serial (hence splitting up large projects into many crates is important, but that makes development somewhat more difficult)
2. LLVM itself is pretty slow
3. Generic functions are monomorphized (there’s a unique machine code version of it for every concrete type combination they are called with) to improve runtime performance, but that gives LLVM a lot more work to do - see point 2

Does that laptop have an SSD?

This is a recent example of a problem that required manual intervention or the system would not boot after updates. This happens every now and then on arch, it’s why you should check arch news before updating.

Jokes on you, this happened to me on fedora with an nvidia gpu.

According to this Google accounts for 90% of Chromium code contributions. If Google does not control Chrome anymore, expect them to mostly go away.

FreeBSD is closer to Unix than Linux is

Usually not on every launch, but a lot of first time launch installers require it.

Question is how “real” that support is - firmware updates matter and depend mostly on the chip manufacturer’s support.

By 8 years old even the newest devices will be out of software support and using EOL phones is not a particularly great idea for security. GOS’s security focus goes out the window if you use an old version with known vulnerabilities.

You can probably expect GOS support as long as Google supports the device, that is the main limitation. For the newer Pixels that is promised to be 7 years after release.

Going by this table, Pixel 6 is currently the oldest to get full GOS updates

That matches Google’s software support

This is my favourite

Don’t buy ASUS, they have a terrible security record. At this point I would trust only MikroTik and Ubiquiti.

They exist because they reproduce faster than they die. The fact that they are necessary for some other species is irrelavant to their existance. Such a claim only really makes sense for plants and animals that people farm.

I don’t get the downvotes, Apple is religious about avoiding configuration where not absolutely required.

Apple bumps the version number for everything every year nowadays, so not a problem for them.

That is a consequence of having parallelism - all mainstream pre-Rust memory safe languages with parallelism suffer from this issue, they are still generally regarded as memory safe. I don’t know where you got that Java does not have this issue, you need to know to use the parallelism-safe data types where necessary.

How is Go not memory safe? Having escape hatches does not count, all the safe languages have those.

Due to the way Flatpak deals with nvidia drivers, you need to run flatpak update after any time the nvidia drivers update and you reboot the system. Thankfully you do not need to reboot after updating only flatpaks. Could not find a good source for this now, unfortunately.

As for the “why?” - flatpak apps do not contain the userspace parts of the nvidia driver required to use the GPU properly, they come packaged as separate runtimes. These nvidia driver runtimes need to match the specific driver version you are currently running. If they don’t match, flatpak downloads the right runtimes when updating.

Yep, reinvent it for educational purposes and then burn it with fire.

Is it? Honestly I don’t care about it anymore, I’ve been opening everything from task bar icons and search for ages now.