3 ms·
The problem with any of these directed-graph based "histories of programming languages" is that they ignore the fact that languages change. Sure, neither Haskel
by lalaithion 6y ago
The problem with any of these directed-graph based "histories of programming languages" is that they ignore the fact that languages change. Sure, neither Haskell nor Ocaml are descendants of the other, but features in one have inspired features in the other countless times, making both languages better. The same goes for Ruby and Python, Java and many of the other languages on this chart and not on this chart, and more generally, all languages. Java introduced generics in 2004. Python introduced garbage collection in 2000.
- bhaak 6y agoThe author addresses that further down on the page: "The diagram only shows influences in the original language design, not influences absorbed through the evolution of the language." If you only are interested in "programming language design" this is not a bad idea. Changes and additions to a language often don't fit well into a language's overall design.
- ncmncm 6y agoIndeed, current C++ is strongly influenced by the MLs. But after 1985.