> the dogma of RESTful APIs consistently push the complexity of data synchronization to the front-end. Sigh. I guess we'll never clarify this point but... as o

> the dogma of RESTful APIs consistently push the complexity of data synchronization to the front-end. Sigh. I guess we'll never clarify this point but... as originally defined, RESTful APIs bear no absolutely no resemblance to modern HTTP APIs that happen to speak content-type: application/json. REST means (quite literally) returning hypermedia representations. To be clear, the industry adopted a dogma of "HTTP JSON APIs" and called it REST by shear mistake. I'm not just pointing out a naming error - these JSON APIS do not follow REST. They have consistently pushed the complexity of data synchronization to the front end. 100% on purpose in most cases. And we're paying for it. Author nailed that part. But that's totally different than REST. The REST hypermedia approach has explicitly outlined a viable alternative to this madness! Keep state on the server, make everything a representation of that state, then transfer it as requested over HTTP. The word "REST" had been hijacked to the point where it literally means the opposite of what the author intended.