Comment by tomashubelbauer

We've seen some interactive education projects on HN (the famous page on raytracing, the one where there's everything about curves, many audio-based projects) and they have had great reception. I think the reason why most devs still prefer plain-text resources over anything else is two-fold: interactive stuff tends to be less standard (because there isn't really a good standard for it) and harder to version than text, but also for interactive education/documentation tools to be accepted, they need to meet a certain high bar of quality, otherwise they are just eye-candy with insufficient value-add. When developing such tools, I believe there is a point of immersion after which they clearly become superior to text materials to most people including otherwise text-heavy devs, but if an author of such interactive tool fails to reach this level, their work is seen as a distraction, because you still need to refer elsewhere. Stack Overflow's documentation examples (as much as I really wished the initiative would succeed) were very far from reaching this bar. They were not organized well, lackluster and were not interactive enough either.