joe armstrongErik Porter, Charles, Mike Sampson, Grace Francisco, Brian Keller, Nathan Heskew, dshadle, Dan Fernandez, Duncan Mackenzie, Jeff Sandquisthttp://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.pnghttp://channel9.msdn.com/tags/Joe+Armstrong/joe armstronghttp://channel9.msdn.com/tags/Joe+Armstrong/en-usTue, 30 Oct 2007 19:59:59 GMTTue, 30 Oct 2007 19:59:59 GMTEvNet (EvNet, Version=1.0.3608.3122, Culture=neutral, PublicKeyToken=null)<p>Often, after the camera is turned off, the conversation continues and, on occasion is truly interesting. Of course, as you could image, Joe, Erik and I continued to chat about concurrent programming, functional languages, the future of hardware-software interaction, etc, when I turned the camera off after <a href="http://channel9.msdn.com/showpost.aspx?postid=351659>part 1</a> of this interview with the creator of Erlang, Joe Armstrong.<br /> <br /> Rather than let the conversation evaporate into the ether of time and space, I decided to turn the camera back on and record a second part. I am sure glad I did! <br /> <br /> This time around, Erik Meijer sits down in the other hot seat and we embark on a fascinating conversation about the future of programming in an increasingly, from a modern hardware + software perspective, concurrent world.<br /> <br /> Joe is outspoken on the topic of objects and mutable shared state, as you know from part 1 of this interview (and if you understand Erlang, obviously). He's also got some really interesting ideas on programmable hardware...<br /> <br /> In this interview, you will also learn what got the great Erik Meijer interested in programming and languages. It's a really interesting story.<br /> <br /> Tune in. This is another compelling conversation with some of the industry's most innovative thinkers. Enjoy!</p> <p><strong><a href="http://armstrongonsoftware.blogspot.com/"><span>Joe Armstrong</span></a></strong> is the principle inventor of the Erlang programming Language and coined the term "Concurrency Oriented Programming". He has worked for Ericsson where he developed Erlang and was chief architect of the Erlang/OTP system.</p> <p>In 1998 he left Ericsson to form Bluetail, a company which developed all its products in Erlang. In 2003 he obtain his PhD from the Royal Institute of Technology, Stockholm. The title of his thesis was "Making reliable distributed systems in the presence of software errors." Today he works for Ericsson.</p> <p>He is author of the book <a href="http://www.pragmaticprogrammer.com/titles/jaerlang/"><span>Software for a concurrent world</span></a>: (Pragmatic Bookshelf - July 15, 2007). He is married with 2 children, 2 cats and 4 motorcycles and would very much like to sell his Royal Enfield Bullet and replace it with a Norton Commando.</p><img src="http://channel9.msdn.com/249537/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" />http://channel9.msdn.com/posts/Charles/JAOO-2007-Joe-Armstrong-On-Erlang-OO-Concurrency-Shared-State-and-the-Future-Part-2/Often, after the camera is turned off, the conversation continues and, on occasion is truly interesting. Of course, as you could image, Joe, Erik and I continued to chat about concurrent programming, functional languages, the future of hardware-software interaction, etc, when I turned the camera off after part 1 of this interview with the creator of Erlang, Joe Armstrong. Rather than let the conversation evaporate into the ether of time and space, I decided to turn the camera back on and record a second part. I am sure glad I did! This time around, Erik Meijer sits down in the other hot seat and we embark on a fascinating conversation about the future of programming in an increasingly, from a modern hardware + software perspective, concurrent world. Joe is outspoken on the topic of objects and mutable shared state, as you know from part 1 of this interview (and if you understand Erlang, obviously). He's also got some really interesting ideas on programmable hardware... In this interview, you will also learn what got the great Erik Meijer interested in programming and languages. It's a really interesting story. Tune in. This is another compelling conversation with some of the industry's most innovative thinkers. Enjoy! Joe Armstrong is the principle inventor of the Erlang programming Language and coined the term "Concurrency Oriented Programming". He has worked for Ericsson where he developed Erlang and was chief architect of the Erlang/OTP system. In 1998 he left Ericsson to form Bluetail, a company which developed all its products in Erlang. In 2003 he obtain his PhD from the Royal Institute of Technology, Stockholm. The title of his thesis was "Making reliable distributed systems in the presence of software errors." Today he works for Ericsson. He is author of the book Software for a concurrent world: (Pragmatic Bookshelf - July 15, 2007). He is married with 2 children, 2 cats and 4 motorcycles and would very much like to sell his Royal Enfield Bullet and replace it with a Norton Commando.http://channel9.msdn.com/posts/Charles/JAOO-2007-Joe-Armstrong-On-Erlang-OO-Concurrency-Shared-State-and-the-Future-Part-2/Tue, 30 Oct 2007 19:59:00 GMThttp://channel9.msdn.com/posts/Charles/JAOO-2007-Joe-Armstrong-On-Erlang-OO-Concurrency-Shared-State-and-the-Future-Part-2/13138http://channel9.msdn.com/249537/WebViewBug.aspx?EVT=0Often, after the camera is turned off, the conversation continues and, on occasion is truly interesting. Of course, as you could image, Joe, Erik and I continued to chat about concurrent programming, functional languages, the future of hardware-software interaction, etc, when I turned the camera off after <a href="/showpost.aspx?postid=351659">part 1</a> of this interview with the creator of Erlang, Joe Armstrong.<br /> <br /> Rather than let the conversation evaporate into the ether of time and space, I decided to turn the camera back on and record a second part. I am sure glad I did! <br /> <br />CharlesCharles6http://channel9.msdn.com/posts/Charles/JAOO-2007-Joe-Armstrong-On-Erlang-OO-Concurrency-Shared-State-and-the-Future-Part-2/RSS/http://channel9.msdn.com/249537/Trackback.aspxErik MeijerErlangFunctional ProgrammingHardwareJAOO2007Joe ArmstrongProgrammingI recently got the chance to attend <a href="http://www.jaoo.org/conference/"><span>JAOO</span></a> in Aarhus, Denmark. Besides learning a great amount about various approaches to solving hard problems that we all face as programmers (regardless of the stack we spend most of our time developing on), I got to meet so many interesting people from all walks of programmer life. <p><strong><a href="http://armstrongonsoftware.blogspot.com/">Joe Armstrong</a></strong> is the principle inventor of the Erlang programming Language and coined the term "Concurrency Oriented Programming". He has worked for Ericsson where he developed Erlang and was chief architect of the Erlang/OTP system.</p> <p>In 1998 he left Ericsson to form Bluetail, a company which developed all its products in Erlang. In 2003 he obtain his PhD from the Royal Institute of Technology, Stockholm. The title of his thesis was "Making reliable distributed systems in the presence of software errors." Today he works for Ericsson.</p> <p>He is author of the book <a href="http://www.pragmaticprogrammer.com/titles/jaerlang/" target="_blank">Software for a concurrent world</a>: (Pragmatic Bookshelf - July 15, 2007). He is married with 2 children, 2 cats and 4 motorcycles and would very much like to sell his Royal Enfield Bullet and replace it with a Norton Commando.<br /> <br /> <strong><a href="http://blogs.msdn.com/madst/default.aspx">Mads Torgersen</a></strong> is a Senior Program Manager in the C# group and has been working on the design of LINQ and other new C# language features. Before joining Microsoft, Mads worked as an associate professor in computer science at the university of Aarhus, where he was part of the group that developed wildcards for Java generics.<br /> <br /> Here, in part one of a two part interview, Joe and Mads discuss the pros and cons of object oriented programming, the new spotlight on concurrency and the future of languages (it should come as no surprise, for those of you who understand Erlang, that Joe is not a big time proponent of OO...). Erik Meijer, who is listening into the conversation will appear at random intervals to add his usual brilliant perspective.<br /> <br /> This is a fantastic discussion. Listen in and learn from some of programming's masters. This was a real treat for me and one of the highlights of my time at JAOO.</p><img src="http://channel9.msdn.com/249535/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" />http://channel9.msdn.com/posts/Charles/JAOO-2007-Joe-Armstrong-On-Erlang-OO-Concurrency-Shared-State-and-the-Future-Part-1/I recently got the chance to attend JAOO in Aarhus, Denmark. Besides learning a great amount about various approaches to solving hard problems that we all face as programmers (regardless of the stack we spend most of our time developing on), I got to meet so many interesting people from all walks of programmer life. Joe Armstrong is the principle inventor of the Erlang programming Language and coined the term "Concurrency Oriented Programming". He has worked for Ericsson where he developed Erlang and was chief architect of the Erlang/OTP system. In 1998 he left Ericsson to form Bluetail, a company which developed all its products in Erlang. In 2003 he obtain his PhD from the Royal Institute of Technology, Stockholm. The title of his thesis was "Making reliable distributed systems in the presence of software errors." Today he works for Ericsson. He is author of the book Software for a concurrent world: (Pragmatic Bookshelf - July 15, 2007). He is married with 2 children, 2 cats and 4 motorcycles and would very much like to sell his Royal Enfield Bullet and replace it with a Norton Commando. Mads Torgersen is a Senior Program Manager in the C# group and has been working on the design of LINQ and other new C# language features. Before joining Microsoft, Mads worked as an associate professor in computer science at the university of Aarhus, where he was part of the group that developed wildcards for Java generics. Here, in part one of a two part interview, Joe and Mads discuss the pros and cons of object oriented programming, the new spotlight on concurrency and the future of languages (it should come as no surprise, for those of you who understand Erlang, that Joe is not a big time proponent of OO...). Erik Meijer, who is listening into the conversation will appear at random intervals to add his usual brilliant perspective. This is a fantastic discussion. Listen in and learn from some of programming's masters. This was a real treat for me and one of the highlights of my time at JAOO.http://channel9.msdn.com/posts/Charles/JAOO-2007-Joe-Armstrong-On-Erlang-OO-Concurrency-Shared-State-and-the-Future-Part-1/Mon, 29 Oct 2007 18:05:00 GMThttp://channel9.msdn.com/posts/Charles/JAOO-2007-Joe-Armstrong-On-Erlang-OO-Concurrency-Shared-State-and-the-Future-Part-1/25893http://channel9.msdn.com/249535/WebViewBug.aspx?EVT=0I recently got the chance to attend JAOO in Aarhus, Denmark. Besides learning a great amount about various approaches to solving hard problems that we all face as programmers (regardless of the stack we spend most of our time developing on), I got to meet so many interesting people from all walks of programmer life. Joe Armstrong is the principle inventor of the Erlang programming Language and coined the term "Concurrency Oriented Programming". He has worked for Ericsson where he developed Erlang and was chief architect of the Erlang/OTP system. In 1998 he left Ericsson to form Bluetail, a…CharlesCharles18http://channel9.msdn.com/posts/Charles/JAOO-2007-Joe-Armstrong-On-Erlang-OO-Concurrency-Shared-State-and-the-Future-Part-1/RSS/http://channel9.msdn.com/249535/Trackback.aspxErik MeijerErlangJAOO2007Joe ArmstrongProgramming