I like programming languages. I like learning how they work, why their designers made particular tradeoffs and how a language changes once a community starts using it for problems its creator did not anticipate.
I also love history. The good kind does more than arrange events on a timeline: it explains the constraints, personalities and arguments that made one outcome possible while closing off others. Programming languages have plenty of all three. Their histories are computer history.
CultRepo has produced three documentaries that sit neatly at that intersection. They cover Clojure, C++ and Python through interviews with the people who designed, implemented, extended and adopted them. These are not feature tours or syntax lessons. They are stories about how software gets made and how it survives contact with the world.
Clojure: simplicity is not easy
The Clojure documentary begins with Rich Hickey’s sabbatical project and follows an idea that challenged how many programmers thought about state. Its recurring subjects are simplicity, time, identity and immutable data: concepts that sound abstract until they determine whether a concurrent system remains understandable.
The film also follows Clojure beyond its creator. Contributors explain how the language and its community developed, while Nubank provides the large-scale production story. That combination matters. A language is more than its initial design, and the documentary shows what happens when a stubborn set of ideas acquires users, libraries and institutional weight.
C++: a language that refuses to disappear
The C++ documentary traces the language from Bjarne Stroustrup’s work at Bell Labs and C with Classes through the original Cfront compiler, standardization and the modern C++ community. Stroustrup is joined by people who shaped important parts of that history, including Alexander Stepanov, whose work led to the Standard Template Library.
C++ is an especially good subject for this treatment because its history is full of competing requirements. It had to remain useful to C programmers, support higher-level abstractions, run efficiently and evolve without casually abandoning an enormous installed base. People still argue about the result. They also continue to build operating systems, browsers, games, trading systems and countless other pieces of infrastructure with it. The film explains how both facts can be true.
Python: the side project that took over
The Python documentary starts before Python itself, with the ABC language and the Amoeba distributed system at Centrum Wiskunde & Informatica (CWI). It then follows Guido van Rossum’s early implementation, the open-source release, the growing community and the creation of institutions capable of carrying the language forward.
The story does not pretend that this growth was automatic. The Python 2 to Python 3 transition receives the space it deserves, as do disputes over governance and Guido’s eventual departure as benevolent dictator for life (BDFL). The later expansion into web development, scientific computing, data science and machine learning makes more sense after seeing the community decisions and occasional near misses that came first.
Watched together, the three documentaries make a useful point. Programming languages do not emerge fully formed from a grammar and a clever type system. They are shaped by hardware, previous languages, employers, standards bodies, open-source communities and arguments that may take decades to resolve.
That is why these films are worth watching even if you do not write Clojure, C++ or Python. They document how ideas become infrastructure. That is programming-language history, and programming-language history is computer history.