2 ms·
At the lowest layer, it's electrons moving through transistors or quantum mechanics or quarks or turtles or what have you. It's all a question of relevant abstr
by brudgers 7y ago
At the lowest layer, it's electrons moving through transistors or quantum mechanics or quarks or turtles or what have you. It's all a question of relevant abstractions. I'm not being dismissive because it is hard to accept that object oriented programs quickly become indistinguishable from functional programs as we move down the stack.
It's really a question of what our chosen abstraction allows us to take for granted. If we're worried about what we take for granted, then we need to be wary of "just" as in "just polling." Because polling entails scheduling and efficient scheduling is NP hard and the code that implements the scheduling abstraction at the layer of the kernel abstraction is almost certainly of greater inherent complexity than the code written at the application abstraction layer that utilizes the asyncio abstraction because the kernel abstraction layer has to deal with multiple hardware threads and predictive execution and pipelining and multiple magnitudes of latency for lots and lots of processes pooled together.
If you're interested in diving down, I recommend The Design of the Unix Operating System by Bach. It has clear diagrams and language that show the big ideas happening below the application layer.
- kureikain 7y agoThanks for that book introduction. I absolutely will check it out.