Will Crichton

Cleve Moler presented about the history of Matlab. Turns out Matlab stands for "Matrix Laboratory", which .... I'm surprised I didn't know.

He noted that the first version of LabVIEW was used more broadly than anticipated. All kinds of scientists felt empowered to run their own programs. Also he credited their willingness to see the potential in LabVIEW and overlook its initial flaws (eg lack of undo).

Steve Naroff on creating Clang: "We were using LLVM married with GCC to do dynamic optimizations at runtime [...] But I wanted a frontend for LLVM to have a compiler that could live entirely at runtime. GCC was not well-equipped to do that."

Notably, many more HOPL papers this time came from domain-specific languages: Matlab, LabVIEW, R, Logo, Verilog. With Dr. Shaw's keynote, they mark a shift towards recognizing the huge range of application areas that programming languages cover today.

Allen Wirfs-Brock and Brendan Eich are talking about Javascript in 2 minutes. If you have a bone to pick with everyone's favorite language, maybe I can pass along your pointed question!

"ECMA decided to base its specification on Microsoft's JS standard, partially because it was written in Microsoft Word which was the word processor that ECMA used."

Javascript has probably the most interesting, winding language path of any today. Such a product of intertwined social, economic, and technical factors.

- Conceived as Scheme - Implemented in 10 days as a Scheme/Java clone baby - But couldn't be too like Java (no classes) - But still needed Java syntax - Initial specification written by MS engineers that reverse-engineered it from Netscape's initial release

- Turned into a committee language, but no one could agree on it - Rejected version turned into ActionScript - Refined version of ActionScript implemented in SML turned into ES4, also rejected - Progress stopped when MS won 96% browser share w/ IE, until Firefox reignited the war

- Frustrated users wrote languages to transpile to Javascript, influencing iterations down the line - Insane users transpiled C++ into Javascript, birthing the need for WebAssembly - And Javascript eventually got classes!

"In a language for learners, we still believe [dynamic scoping] is the correct choice. If a variable exists, it's visible."

A version of Logo was developed for Atari, which apparently was once in the PC industry. They even had Alan Kay as chief scientist! Alan Kay said about his departure from Atari: "I guess the tree of research must from time to time be refreshed with the blood of bean counters.''

Bjarne Stroustrup now presenting the modern history of C++. It's his third paper at HOPL, the only language to appear three times! Testament to the enduring legacy of a time-tested language. (Caveat: I have sworn to never use C++ again. )

"Typical request: * Simplify C++ * Add these two new features * Don't break my code"

Q: Thoughts on dialects, e.g. C++ w/o exceptions? A: I really dislike dialects, because you can't communicate or share. Dialects usually ban features, and that's wrong, the complexity just goes elsewhere. Some of the fastest code I've seen carefully uses exceptions.

Q: Thoughts on Rust and Zig, any influence on C++? A: From what I've seen of Rust, it doesn't fit into my view of C++. I experimented with borrowing ten years ago and found the code got too complicated. We can get type and resource safety without it.

Rich Hickey now discussing the history of Clojure. I've never used Clojure, but I expect to emerge with strong opinions involving words like "complect".

Prediction was incorrect, the right opinion-word was "concretion".

Q: Thoughts on Typed Clojure and using dynamism to manage complexity? A: I don't think C++/Java/etc types are rich enough. If your program is imperative, your problems will be dominated by state. Types cause code to be far more specific and far less reusable than it ought to be.