Actually, I'm not fully sure what the author's main point is. If I had to write a short summary based on my best guess, it would be: "I'm disappointed Erlang didn't catch on more, but the general programming & architectural lessons I learned from using it were still worth the effort". Is that clearly a wrong interpretation?
My post relates to measuring "worth" here, and to the reasons why it probably didn't catch on.
I'm the author.
I'm not really disappointed Erlang didn't catch on more. As I said in the post, I wanted to take a bit of time to reflect over most of that decade, the ladder of ideas, and things that changed.
Re: I'm the author.
Gulp!
I suppose I was looking for a few key ideas/themes as a summary the way we are taught to create and seek out in college writing courses, typically "essay style" you could say. Habit. Instead, it's more of a collection of relatively indendent notes.
That’s why I downvoted you. It’s not because of your opinion, it’s because it’s probably not in the right thread.