3 ms·
Oh I like this game! Using HTTP as a transport for IPC and APIs that don't need to be consumed by a browser. Implementing what is really RPC and trying to shoeh
by robmccoll 12y ago
Oh I like this game! Using HTTP as a transport for IPC and APIs that don't need to be consumed by a browser. Implementing what is really RPC and trying to shoehorn it into REST when RPC is the right choice for the design. Javascript and the reinvention and rediscovery of old ideas in javascript. Any interpreter that could be replaced with LLVM backed JIT. Automake. Java. XML. JSON that's intended to be written by humans (love JSON for human readable structured data but for configuration files, let's stick to Unix/INI/TOML). Go's import system. "Vendoring". The lack of a standardized and properly compatible C++ ABI (what if we just went back to cross compiling to C CFRONT style?). DSLs. The habit of removing constraints from a problem and then compairing your solution to the previous solutions that solve with the original constraints to show how simple, performant and totally revolutionary your new idea is (looking at you eventual consistency key value stores). And this list goes on for a while because I'm apparently a cantankerous old man...