alt Hacker NewsThe problem is that treating the incorrect simplification as good can be very tempting for teachers.
For example, in an introductory physics course teaching Newtonian dynamics without the brutal complications of special relativity and general relativity is fine because it doesn't take much to explain that it is an approximation and it is good enough for "everyday" situations. Students are aware that a better model is available: worst case, they try to get away with not using it.
On the other hand in an introductory programming course teaching that if you have Animals in the program the dog instances "should" belong to a Dog subtype is logically consistent and elegant; the only opposing force is the abstract and uncool engineering principle of keeping software simple, and many teachers are dogmatic and enthusiastic.
Everything seems drastically simpler after you've already learned it vs when you're trying to learn everything about it for the first time. Hell, even explaining what the difference between a class and a struct is in C++ ends up going into weeds about public/private that makes many people who just learned what variables were a few weeks ago, let alone trying to teach them what different attributes of classes do by comparing best practices of their usages.
I.e. they aren't trying to say what is elegant yet, they are just trying to get people to understand what the building blocks of classes they can compare are even supposed to do so they can get to comparing when you'd do different ones.
But there are bad teachers and they tend to be bad regardless of the example chosen.