The argument is that it's much easier to secure proper key material rather than design and config information that can often be leaked accidentally because it's actually directly manipulated by humans (employee onboarding, employee churn etc)

The only other ISA I know of that did something similar was the Am29000

The Am29000 modeled it in an interesting way though:

The register file consisted of 128 global registers but the instruction encoding allowed to specify an "indirect register index" mode where the operand register was computed from the content of gr1 plus an offset. Thus gr1 acted as a "register window stack pointer". I _think_ such a computed register index would then be used to index into a separate register file for locals (and arguments etc) but I'm not sure.

Anybody here is familiar with this quite old ISA?

(I'm really interested in the richness of the CPU design space, the history of which is fascinating)

My point was that you don't literally have to run the proxy on localhost in order to scope the request.

For example if the proxy runs in localhost you can trust the localhost workload.

Or you can use some other kind of workload identity proof (like cloud based metadata servers). If you leak such a key no other VM can use it, because it's scoped to your VM

so basically ...

you could view this as a kind of discount, but instead of paying less later, you get some cash now and then pay full later.

I think it's reasonable to worry that way before machines are more reliable than the average human (let alone more reliable than a highly trained human) they can pose a significant disruption to the job market which will send shockwaves throughout society

What can possibly go wrong

It's not about where you come from. It's about whether writing is useful or even required for some aspects of civilization to develop.

Spain, Argentina, Kenya, Indonesia, Kuwait and countless other countries haven't bombed any civilian infrastructure either and yet they will be affected by the aggressive posture around international maritime traffic.

Are you expecting that Iran will not apply the fee to ships that sell oil Malesia or South Africa?

1. You can write a spec that builds something that is not what you actually wanted

2. You can write spec that is incoherent with itself or with the external world

3. You can write a spec that doesn't have sufficient mechanical sympathy with the tooling you have and so it requires you to all spec out more and more of the surrounding tech than you practically can.

All of those issues can be addressed by iterating on the spec with the help of agents. It's just an engineering practice, one that we have to become better at understanding