> I’d argue that at scale, those ‘efficient’ protocols waste probably 100x more developer time troubleshooting In another comment you said there should be num

> I’d argue that at scale, those ‘efficient’ protocols waste probably 100x more developer time troubleshooting In another comment you said there should be numbers to back this sort of claim Anyway, the problem with our software stack is that there are so many layers, so if we get performance wrong at every one of them, it'll compound terribly at the top. We should have some sort of strategy to decide priorities at each layers, say, lower layers like OS, container, programming language, network protocols, should be about performance, then we can be wasteful at higher layers, the domain code, if that gives us better abstractions and maintainability.