SICP is about execution models above theory, C and C++ is about legacy, tooling, subtle nuances and “shoot yourself in the foot or how I stopped worrying and le

SICP is about execution models above theory, C and C++ is about legacy, tooling, subtle nuances and “shoot yourself in the foot or how I stopped worrying and left my job after lunch”. The specific paradigm is almost irrelevant there. If you want a job, pick what’s popular today or gains popularity quickly (as in _/). Otherwise you’ll feel trapped in boring and tedious after a while. If you want to play with low level to understand how it works (but not work in embedded tech), I’d refer to modern low-level languages like Go, Rust (not being fan of) or Nim, or Zig, and read but not write some assembler, just to get feel of the “bare metal”. If by “fundamentals” you mean programming fundamentals, not hardware ones, practical languages have not much of it really, I mean they have, most of them have, but it is usually not their selling point or something life-changing. You don’t choose languages and paradigms in them, you choose ecosystems and frameworks that help building your solutions. Lisp/scheme already may have all the paradigms you’ll ever meet, but nobody uses them until the sun goes down.