For example, many millennial have this strange idea that C and C++ are the only option for native AOT compiled code, with language features for cache control, RAII or system programming in general.
The aren't the only option, they became the only option given the decisions that the OS vendors took regarding which languages to sell to their customers on the OS SDKs.
Many of those decisions weren't taken in terms of language quality, rather due to money as UNIX was a free OS, whereas other OSes with better Rust like safety were of course more expensive than free.
So young developers get taught this myth that C was the first system programming language, when in the mid-60's we already had mainframe systems being programmed in type safe systems programming languages, across the whole stack.
Using languages like NEWP (https://en.wikipedia.org/wiki/NEWP), just to give one example. A language where one already had the distinction between safe and unsafe modules, with unsafe modules requiring administrator privileges to run.
But if you prefer more in-depth information:
https://en.wikipedia.org/wiki/Burroughs_large_systems
http://www.cs.virginia.edu/brochure/images/manuals/b5000/bro...
http://www.smecc.org/The%20Architecture%20%20of%20the%20Burr...
We may as well remember Lucy, the former vacuum tube assembler and current resident of the dustbin of history.