Devastating. I'd like to point out a recent tweet @joeerl shared [0][1] that contained things he felt were good wisdom but lost over time: -- Ideas that we forgot: 1. Flow based programming. 2. Pipes. 3. Linda Tuple Spaces. 4. Hypertext (=/= HTML). Computer Science 101: 1. Observational equivalence. 2. Isolation. 3. Composition. 4. Causality. 5. Physics. Two papers to read: 1. The Emperor's Old Clothes - ACM. 2. A Pl…
Joe Armstrong has died
131–140 of 206 posts
Re: Joe Armstrong has died
#132Back in 2015, I somehow ended up as part of a panel discussion at the end of a conference. The panel was going to include Joe Armstrong, Don Syme (inventor of F#), Tony Hoare (!), and myself (a nobody compared to any of them). During the conference, I wanted to meet each of the other folks on the panel, and ended up in a somewhat lengthy conversation with Joe Armstrong -- mostly about Erlang, but at some point the pa…
quite interesting having to see again an estimation system based on primates size comprehension. it is supposed to use the brains but instead of this, it always ends up with primate comparison horseshit. because if you are talented, you already bypass monkey thinking patterns and can honestly express your thought.
Re: Joe Armstrong has died
#133I sent an email asking some seriously noobey questions about concurrency (about why mutation was bad, what made the Actor model work, etc), and instead of a response like "Go read a book and stop bothering me", he responded back with an incredibly long, well-written email explaining a lot of the minutia of how Erlang avoids a lot of pitfalls and generic concurrency theory. He was really good about explaining things in a way simple-enough for me to understand, without coming off as patronizing or rude.
About a year later I got a job doing Erlang, and I sent him another email telling him this, saying something to the effect of "sorry for bothering you a year ago, but your email was really helpful to me".
His response was basically "You have nothing to apologize for! I've always thought it was important to help people asking questions, especially early in their career".
I can honestly say that his kindness and patience changed my life for the better. If he hadn't held my hand a bit to make distributed systems make sense to me, there's a very high likelihood that I would still be writing Flash applications for a Tae Kwon Do studio.
RIP Joe, you will be missed.
Re: Joe Armstrong has died
#134Years ago I emailed Joe Armstrong about concurrency stuff. I had no idea about anything like multithreaded programming or distributed systems or anything like that, but I had read Erlang was a language well-suited for that stuff. I sent an email asking some seriously noobey questions about concurrency (about why mutation was bad, what made the Actor model work, etc), and instead of a response like "Go read a book and…
Re: Joe Armstrong has died
#135Years ago I emailed Joe Armstrong about concurrency stuff. I had no idea about anything like multithreaded programming or distributed systems or anything like that, but I had read Erlang was a language well-suited for that stuff. I sent an email asking some seriously noobey questions about concurrency (about why mutation was bad, what made the Actor model work, etc), and instead of a response like "Go read a book and…
Re: Joe Armstrong has died
#136Years ago I emailed Joe Armstrong about concurrency stuff. I had no idea about anything like multithreaded programming or distributed systems or anything like that, but I had read Erlang was a language well-suited for that stuff. I sent an email asking some seriously noobey questions about concurrency (about why mutation was bad, what made the Actor model work, etc), and instead of a response like "Go read a book and…
Re: Joe Armstrong has died
#137Years ago I emailed Joe Armstrong about concurrency stuff. I had no idea about anything like multithreaded programming or distributed systems or anything like that, but I had read Erlang was a language well-suited for that stuff. I sent an email asking some seriously noobey questions about concurrency (about why mutation was bad, what made the Actor model work, etc), and instead of a response like "Go read a book and…
Are you willing to share his reply?
Re: Joe Armstrong has died
#138I'm so sad and shock. He just became mod at elixirforum.com
Re: Joe Armstrong has died
#139Years ago I emailed Joe Armstrong about concurrency stuff. I had no idea about anything like multithreaded programming or distributed systems or anything like that, but I had read Erlang was a language well-suited for that stuff. I sent an email asking some seriously noobey questions about concurrency (about why mutation was bad, what made the Actor model work, etc), and instead of a response like "Go read a book and…
Re: Joe Armstrong has died
#140I was following him on Twitter, and it was always amazing that a genius like him took the time to respond to people on Twitter with insightful comments. Showed what a great human being he was. RIP Joe.