AMD CPUs basically all boost up to 90°C as a relatively normal operating temperature as long as the power (and some other factors) allow it to. I assume AMDs and NVs GPUs do to, but I play mostly CPU bound games so I see mine just sitting at ~60°C under load.

429 is if you have been rate limited. 529 is for server overloaded and can't process more.

I really hate the `curl <url> | sh` specifically because if your connection drops at a specifically unlucky point in time you are left with a partially executed script which if you are unlucky enough may just have been executing `rm -r ~/.cache/<pkg>/download` but it stopped at `rm-r ~/`.

Is it likely? No. Can it happen? Yea.

Just make it `curl -o <file> <url> && sh <file>` and this entire problem is gone.

Most scripts now put all the code into a shell function and call it in the last line of the script, so this bug can't happen.

Correct, and/or in addition, most nowadays prepend something like `set -euo pipefail` to the scripts in the line immediately after the shebang which results in stopping on errors, including things such as syntax errors stemming from e.g. incomplete installer transmission over wire.

(At least for bash scripts, I’m not sure whether these are POSIX syntax to be frank.)

Do note that being able to completely remove MS keys is highly dependent on your mainboard. Not in the sense of if they allow you to do it (I think most if not all DIY boards allow you to), but if you will be able to boot afterwards.

I (soft?)bricked a mainboard and it doesn't want to boot anymore after I removed the MS keys. The worst part is, that it has a dualBIOS and no active switch to change between them, only their own "I'll change when I see issues"... well you can guess how well that worked out (and I am not able to get it to clear CMOS for some reason).

Both Steam and Battle.net use CEF for their UI as well. And IMO they are on 2 ends of the "nice to use" from the implementation side (Steam being a sluggish hell and B.net being nice). Though then again B.net is only for Blizzard games, so they can also optimise for the limited set games.

> Steam being a sluggish hell

news to me. Been using steam since it launched. Never noticed it being sluggish

You haven't? Steam has been a miserable experience for years. Great way to make a monster gaming rig replicate the eMachines 1998 experience.

I'm so sincerely glad that 28 years later I get to spot hate for eMachine in the wild. What an absolute piece of shit. I remember buying one and immediately returning it and to this day... you get it.

If we are generous and assume a review speed of 1 line per second, that is still over 11 continuous uninterrupted days of review by a single person.

In that case I would expect them to try and work something out with AMD directly instead of building a company on undocumented features.

Not even that, AUR packages are just git repos, they don't auto update unless you use an AUR helper that does. You literally can just clone it and makepkg it and then pacman also tracks the installed files and uninstalling is a breeze.

> this way i don't have to use root when building

`makepkg` will actively refuse to run if you are invoking it as root (unless you specifically invoke it with something like `env EUID=123 makepkg ...`).

> and can have program installed locally just for a single user which is how it should be anyway for most desktop use cases.

I do wish pacman would support a user level installations. It will refuse to install packages as non-root (which you can go around by using user namespaces and mapping yourself to root).

Maybe I used imprecise wording. Not root, but must be part of sudoers. Or am I misunderstanding how the process works? Don'tWhenever I have installed a package from aur with yay it requires user being part of sudoers.

Yea, but that is to install the package after it was built (or installing dependencies). The build itself is done unprivileged.

GP was talking about why Arch isn't used in enterprise, not what happened in the post.