

The only one I think is reasonable is GraphQL. But that isn’t rest, and HTTP is just one of the transport layers it supports.
For anything claiming to be RESTful, it’s a crime.
The only one I think is reasonable is GraphQL. But that isn’t rest, and HTTP is just one of the transport layers it supports.
For anything claiming to be RESTful, it’s a crime.
(another pet peeve of mine is “rest” APIs that use 200 response codes for everything)
Yup, also some APIs use GET for everything. It’s a pain. And it means that filtering by verb only helps if you’re intimately familiar with the API. And even then, only if you keep up with changes as they happen. So really, only if you’re developing the API yourself.
That’s not exactly how it works. There are “territorial waters” which are entirely under the control of the state. And there is the “exclusive economic zone” (EEZ) outside of that, where the state has rights to resources. But the surface is “international waters”. This incident happened in the EEZ.
This only works if there is enough supply from those other companies. This also assumes that the other companies have a supply chain that isn’t affected by tariffs. Which means each step on the chain needs to produce enough to be a reasonable alternative to tariffed imports.