>It's a family of OSes written by the kind of people who think if you grow a beard and stare very hard at your C code it will become secure and bug free.
Staring hard at a set of C primitives and learning the way the primitives actually utilize modern hardware and compose is a fundamental part of computing. Part of programming is not just writing your code in the sense of what it does, but also knowing what it doesn't. All computation is at the bottom deterministic. We've just piled on so much abstraction (if not in high-level languages then in shit like uCode) that most practitioners will just tell you to embrace the madness of unbounded abstraction. You don't have to follow their advice. Tighter code is yours for the taking. Learn your hardware.
The price though tends to be portability. Also, compiler writers are completely deranged, and known for completely turning shit on it's head. Read your language spec, embrace your debugger, and go with God.
Staring hard at a set of C primitives and learning the way the primitives actually utilize modern hardware and compose is a fundamental part of computing. Part of programming is not just writing your code in the sense of what it does, but also knowing what it doesn't. All computation is at the bottom deterministic. We've just piled on so much abstraction (if not in high-level languages then in shit like uCode) that most practitioners will just tell you to embrace the madness of unbounded abstraction. You don't have to follow their advice. Tighter code is yours for the taking. Learn your hardware.
The price though tends to be portability. Also, compiler writers are completely deranged, and known for completely turning shit on it's head. Read your language spec, embrace your debugger, and go with God.