> JSON Patch is not REST. It is not representational state. This is a perfectly reasonable take, although it fits well in systems otherwise generally more incl

> JSON Patch is not REST. It is not representational state. This is a perfectly reasonable take, although it fits well in systems otherwise generally more inclined to use HTTP semantics. I know that’s not REST, but it’s certainly easier to reason about and clearly document (eg OpenAPI) than its RPC analogues. > But it's also not the way any sane person has ever done RPC over HTTP. Why not? Aside: I’ve also used it as a format for internal calls and change tracking. It’s surely not ideal, but it was already in the service and trivial to repurpose. Turned out to be an extremely lucky decision, as it also became a crucial tool for forensic analysis in a major recovery effort. > I work in an industry of idiots. You could just… not be a jerk. You have that option.