Me here, who knows http and parts of underlying stack, but doesn’t like to use it as is (I mean in /api/ realm). In my personal programming I’d rather abstract

Me here, who knows http and parts of underlying stack, but doesn’t like to use it as is (I mean in /api/ realm). In my personal programming I’d rather abstract from http[s] and use it as yet another communication layer that carries rpc over ssl in a browser, where there is no alternative. Aka 200-json guy, except for true files/content or lower level errors. REST’s “let’s imagine all our calls are bureaucratic statements and directives with vaguely predefined status codes” just doesn’t click for me.