Well of course comparing state of the art jsonrpc with spaghetti rest will give jsonrpc a headstart

In truth the error is in the premise “we switched rest because everyone’s doing it/is the way webservices are developed now”

Well, no, and that’s the issue with most “rest” api that actually are jsonrpc with html verbs (and ignoring that using json for rest is impossible to begin with): they were written to hit a bullet point on a feature list