Joe Armstrong
Father of Erlang
Joe Armstrong is one of the inventors of Erlang. When at the Ericsson computer science lab in 1986, he was part of the team who designed and implemented the first version of Erlang. He has written several Erlang books including Programming Erlang Software for a Concurrent World
.
Joe held the first ever Erlang course and has taught Erlang to hundreds
of programmers and held many lectures and keynotes describing the
technology.
Joe has a PhD in computer science from the Royal Institute of Technology in Stockholm, Sweden and is an expert in the construction of fault tolerant systems. Joe was the chief software architect of the project which produced the Erlang OTP system. He has worked as an entrepreneurin one of the first Erlang startups (Bluetail) and has worked for 30 years in industry and research.
.
Joe held the first ever Erlang course and has taught Erlang to hundreds
of programmers and held many lectures and keynotes describing the
technology.Joe has a PhD in computer science from the Royal Institute of Technology in Stockholm, Sweden and is an expert in the construction of fault tolerant systems. Joe was the chief software architect of the project which produced the Erlang OTP system. He has worked as an entrepreneurin one of the first Erlang startups (Bluetail) and has worked for 30 years in industry and research.
Joe Armstrong is Giving the Following Talks
What are the important ideas in Erlang?
Erlang Factory SFBay 2010 - Joe Armstrong - What are the important ideas in Erlang? from Erlang Solutions on Vimeo.
Erlang combines ideas from functional programming, logic programming, distributed systems construction, operating systems design and packages these into a platform that can be used for building fault-tolerant scalable systems.
But where did these ideas come from? Which are the most important ideas?
This talk presents a personal view of what I think are the important ideas in Erlang. I'll talk about where the ideas came from and how they developed and changed with time.
I'll also talk about the failed ideas - the ideas we had that lived for a short while, even implemented, and then were removed from the language. The failed ideas are interesting because they often seem to be superficially correct, but on deeper inspection turn out to be wrong.
I'll talk a little bit about some of the ideas which are "good but not yet implemented" usually these represent ideas where behind the scenes their lurks a horribly difficult implementation problem.
But where did these ideas come from? Which are the most important ideas?
This talk presents a personal view of what I think are the important ideas in Erlang. I'll talk about where the ideas came from and how they developed and changed with time.
I'll also talk about the failed ideas - the ideas we had that lived for a short while, even implemented, and then were removed from the language. The failed ideas are interesting because they often seem to be superficially correct, but on deeper inspection turn out to be wrong.
I'll talk a little bit about some of the ideas which are "good but not yet implemented" usually these represent ideas where behind the scenes their lurks a horribly difficult implementation problem.
