And regarding the concept of architectural mismatch, that goes nicely with another thing I recently wrote about [1]: how applying embedded architectures in high

And regarding the concept of architectural mismatch, that goes nicely with another thing I recently wrote about [1]: how applying embedded architectures in high-level languages (Java) seem to yield big gains AND surprise everyone. At the moment I considered it a "lack of vocabulary" in Java, but now I realize that maybe the problem is a bit deeper/more general. Java's architecture (and architecture idioms) might cause a blind spot (or is it a kind of Someone Else's Problem?); while C's architecture/tools or lack thereof disincentivize overwrought (or plain sophisticated) systems, for good and for bad. Or more succinctly, Java makes you stop thinking about how things actually work, while C makes you stop thinking about how things should work. Interesting! [1] https://hmijailblog.blogspot.com/2018/08/you-could-have-invented-lmax-disruptor.html https://hmijailblog.blogspot.com/2018/08/you-could-have-inve...