cognitive psychology. PhD 
Shout-out to @samth!pic.twitter.com/qUeSzuWozf
Show this thread
-
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.
)Show this thread
"Imagine the difficulty of getting agreement on anything of importance in a group that large."pic.twitter.com/Ufm35NFUhr
-
-
"Typical request: * Simplify C++ * Add these two new features * Don't break my code"
Show this thread -
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.
Show this thread -
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.
Show this thread -
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".
Show this thread -
Prediction was incorrect, the right opinion-word was "concretion".
Show this thread -
Hickey on the motivations for Clojure: what makes programming complex?pic.twitter.com/8IgOuevdee
Show this thread -
"Having talks, aimed at specific audiences, about topics that matter, hosted on YouTube, matters."pic.twitter.com/qUpjYMWuRd
Show this thread -
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.
Show this thread -
Q: How did you decide on terms like "concretion" and "complect"? A: I love the dictionary
Eg for complect, I was trying to give more specificity to an old notion, coupling, that system designers understand intuitively.Show this thread -
Btw, I'm not covering every talk in this thread (time constraints, and POPL deadline in 2 weeks lmao). But the papers are all freely available here: https://dl.acm.org/toc/pacmpl/2020/4/HOPL … And the video talks + Q&A will be posted eventually! So be sure to check them out.
Show this thread -
Morten Kromberg presents the post-1978 history of APL. The APL ecosystem initially split around the question: when nesting items in arrays, do those items need to be explicitly "boxed" or not?pic.twitter.com/Ijrm6SZhwV
Show this thread -
Dozens of flavors of APL sprung up in this period. APL was definitively an idea up for grabs, and not a language steered by a single person or org. Probably most like SQL in that regard.pic.twitter.com/8UZwDVm0Vl
Show this thread -
"APL is a notation as much a programming language, and it's important for subject matter experts to be able to use APL on the whiteboard and argue about it. I've seen open source APLs lead to fragmentation, which reduces the value of a notation."
Show this thread -
Stefan Monnier and Michael Sperber presented the history of Emacs Lisp. One focus: modern Elisp has two distinct dialects, dynamically scoped (originally) and statically scoped (added later).
Show this thread -
"Back then, dynamic scoping was considered efficient. Lexical scoping seemed kind of expensive to implement. Lexical scoping requires the creation of closures." Same underlying reason as Logo, but different conclusion (performance vs. learnability)https://twitter.com/wcrichton/status/1406999997527191552 …
Show this thread -
Q: Advice for systems adding dynamic scoping, eg React contexts? A: Picolisp creator said: "Modularity is the ability to reach into a system's guts and make it do what you want." Unconventional, but not wrong. Dynamic scoping enables users to make Emacs do what you want done.
Show this thread -
...The trend at confs like ICFP has been unbreakable abstractions. But systems that result from that, esp editors, are not as flexible at runtime like Emacs. But the balance is hard to find and keep the system comprehensible.
Show this thread -
Don Syme presents the history of F#. Frames it through the lens of the OOP wave of late 90s, and how FP advocates within MSR continued to push for language innovation beyond objects. Found initial F# made for 10x smaller code than C#. 56k LOC for braces! 3k null checks!pic.twitter.com/zur4byC6To
Show this thread -
"When I got to Microsoft, I was told in no uncertain terms that the word 'compositional' was not in the MS vocabulary. And we have blown that apart at MS."
Show this thread -
Q: Aspects of C#/.NET that are hindering F#? A: The big way we suffered is that F# did not have a strong Linux story during the rise of Linux and subsequently the cloud. That's crucial.
Show this thread -
Earlier, several HDL designers discussed Verilog and its ilk. "When we discuss Moore's law, we focus on semiconductor technology... but just as important are the tools used to design the chips. Chips in 1978 were designed with pencil and paper."pic.twitter.com/HdGQ5vL1La
Show this thread -
Sneak peek into the intensive process of naming a language (tag yourself, I'm "logol")pic.twitter.com/92tIyks0oY
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.