This says the UNAS Pro 8 can saturate 20gbe with reads. It won't with just a single user, though, so for homelab enthusiasts it's less attractive even though the price is appealing. But for an actual small business using it to serve a handful of people? The 10gbe isn't a waste

That is exactly why Rust's behavior for +/- operators is a mistake and wrong. It should always panic and anyone that wants something different can specify that in code, where it's clear and explicit.

I don't know if Rust will ever attempt to fix this mistake, but I seriously hope they do.

It lets Rust claim to be UB free without delivering the actual value of being UB free. You still can't rely on a given behavior because it doesn't have one behavior, it has two, and the two behaviors are wildly incompatible with each other.

imo one of those soundness holes is caused directly from trying to prevent UB - integer overflows. It is inconsistent in Rust what happens in that scenario depending on compiler flags, which basically just makes it UB for any given piece of code. And, unfortunately, default release mode behavior is unsafe.

If someone tells you to write a web app, do you also cry? Surely there's more JavaScript frameworks than subsets of C++ at this point, no? Do you also go memorize all of them? Or do you just quickly pick one, and then only learn that one, and forget the rest exist? Because that's kinda how you approach C++. You pick a subset (like, say, just modern C++, only caring about C++17 & later or whatever), and just use that. And move on with your life. There's absolutely no reason to learn how std::auto_ptr works because it's dead in the same way you aren't learning how PHP & CGI works if you're making a modern web app. They're dead relics of the past that you can just pretend don't exist.

You're almost certainly better off with Rust at this point or, if you must have C-like development, Zig.

None of HDR10, HDR10+, or DolbyVision ever answered the question of how to adapt for varying ambient brightness levels, either, which is again a very important question to answer for portable devices like phones, tablets, and laptops.

But at a high level you're basically asking "why doesn't scRGB exist" and, well, it does :) https://en.wikipedia.org/wiki/ScRGB (also called extendedSRGB)

Possibly, but Apple choosing a new, thicker chassis the same generation that they introduce their more power efficient replacement is certainly a thing. Even if Intel failed to achieve the TDP they told Apple, Apple also seems to no longer believe the thinness they were doing was viable for that TDP anyway.

Intel's product offering certainly wasn't as compelling towards the end there, but it also looked almost uniquely bad in Apple's chassis vs everyone else's

Although I'm kinda surprised the DGX Spark used USB-C at all for power instead of just like a DC jack or whatever. But whatever.