We've been holding a Twitter Space weekly on Mondays at 5p for about an hour. Even though it's not (yet?) a feature of Twitter Spaces, we have been recording them all; here is the recording for our Twitter Space for October 18th, 2021.
In addition to Bryan Cantrill and Adam Leventhal, speakers on October 18th included Edwin Peer, Dan Cross, Ryan Zezeski, Tom Lyon, Aaron Goldman, Simeon Miteff, MattSci, Nate, raycar5, night, and Drew Vogel. (Did we miss your name and/or get it wrong? Drop a PR!)
Some of the topics we hit on, in the order that we hit them:
PL/1 belongs more to the problem set than to the solution set
The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offence
APL is a mistake, carried through to perfection. It is the language of the future for the programming techniques of the past: it creates a new generation of coding bums
- @3:08 Languages affect the way you think
It is practically impossible to teach good programming to students that have had a prior exposure to BASIC: as potential programmers they are mentally mutilated beyond hope of regeneration.
- @4:33 Adam's Perl story
- The Camel Book, not to be confused with OCaml
- "You needed books to learn how to do things"
- CGI
- @9:04 Adam meets Larry Wall
- @11:59 Meeting Dennis Ritchie
- "We were very excited; too excited some would say..."
- @15:04
Effects of learning languages, goals of a language, impediments to learning
- Roger Hui of APL and J fame, RIP.
- Accessible as a language value
- Microsoft Pascal, Turbo Pascal
- Scratch
- LabVIEW
- @25:31 Nate's experience
- Languages have different audiences
- @27:18 Human languages
- The Esperanto con-lang
- Tonal languages
- Learning new and different programming languages
- @37:06 Adam's early JavaScript
(tweet)
<SCRIPT LANGUARE="JavaScript">circa 1996
- @44:10
Learning from books, sitting down and learning by typing out examples
- How do you learn to program in a language?
- Zed Shaw on learning programming through spaced repetition blog
- Rigid advice on how to learn
- ALGOL 68, planned successor
to ALGOL 60
- ALGOL 60, was, according to Tony Hoare, "An improvement on nearly all of its successors"
- How do you learn to program in a language?
- @50:41
Where does Rust belong in the progression of languages someone learns?
Rust is what happens when you've got 25 years of experience with C++, and you remove most of the rough edges and make it safer?
- "Everyone needs to learn enough C, to appreciate what it is and what it isn't"
- @52:45 "I wish I had learned Rust instead of C++"
- @53:35 Adam: Brown revisits intro curriculum, teaching Scheme, ML, then Java
- Adam learning Rust back in 2015
(tweet)
"First Rust Program Pain (So you can avoid it…)"
Tom: There's a tension in learning between the people who hate magic and want to know how everything works in great detail, versus the people who just want to see something useful done. It's hard to satisfy both.
- @1:00:02 Bryan coming to Rust
Its concurrency is rooted in CSP, but evolved through a series of languages done at Bell Labs in the 1980s and 1990s, such as Newsqueak, Alef, and Limbo.
- @1:03:01
Debugging Erlang processes. Ryan on runtime v. language
- Tuning runtimes. Go and Rust
- @1:06:42 Rust is its own build system
- @1:11:27
The use of anthropomorphic terminology when dealing with computing systems is a symptom of professional immaturity.
- @1:12:09 Oxide bringup updates
If we got something wrong or missed something, please file a PR! Our next Twitter space will likely be on Monday at 5p Pacific Time; stay tuned to our Twitter feeds for details. We'd love to have you join us, as we always love to hear from new speakers!