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?

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

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

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.

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.

You can just disable web search through the settings app now.

“great work” 🤭

It’s neither with parts from both.

Mastodon can also replace the main FB feed. Matrix would be the closest alternative for Discord, but it has its share of problems.

All the kernel Rust code is GPL, so you can leave that slippery slope alone. MIT licenced core utils just leave the door open to eventually using them in the BSDs as well.