riking

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.

Stripe is still "your bank".

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

Multiple big-O steps faster.

"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.

This is the exact point of the final section of the article, yes.

Nope, you need to run `npm ci` to guarantee that you don't write a new lockfile.

It's because the well got poisoned by marketing teams selling things that were not actually a material improvement over what came before.

What I'm hearing here is "Yes, Google designed their own chip because everything on the market sucks."

ML training is an algorithm that produces an algorithm as output