Rust's no_std does not have access to a reliable clock.

you can just follow one of the "kubernetes on ec2" guides and adapt it to their apis

> electrical/thermal/support power ~= compute power.

Yes, and using larger fans decreases the proportional there. Centralized rectifiers reduces the proportional. Google can make it all the way down to 10% overhead power. That's the point they are making.

Yes, and the question I am asking is how much better are they doing than competition there. For compute density, the real cloud racks are pushing 30-40kW per rack so even if they were 20% and oxide 0%, they don't seem to have a compute density advantage there.

Stripe is still "your bank".

Zelle can't be undone if it's done from your account. They just take the money.

Of course it can. Zelle and your bank may not be keen on doing it, but it’s no less reversible than any other transfer.

And for fraudulent transfers, Zelle’s trying to pin them on the customer is them hoping you’d give up rather than remind them that regulation E governs it as well, and they used to acknowledge that on their web site.

Multiple big-O steps faster.

That's not how big-O works.

"hmm, you call it an 'enum class' yet somehow I cannot define methods on it"

It'll block the multi-login and require you to fully sign out of everything, THEN log into the other organization account.

Typically, the corporate login will be blocked if you attempt this.

> On the other hand, if you make a string of common byte sequences, a couple GB long, and distribute it with every PC...

This is what brotli does.