A Conversation with Bjarne Stroustrup, Carl Hewitt, and Dave Ungar

Download this episode

Download Video

Download captions

Download Captions

Description

What happens when you put three titans of programming language design and computing in a room and turn a camera on to capture what takes place?

That's the thought experiment that led to this conversation with C++ language creator Bjarne Stroustrup, Self language creator Dave Ungar, and actor model creator Carl Hewitt. Thank goodness all three of them were present at Lang.NEXT 2014. Many topics are covered, as you can imagine. It's best that you find some quality time to watch, listen, and learn from some true masters. This is a long conversation and there is great programming history herein!

This is a rare (and very candid) gathering of some of the best minds in the programming world today.

Huge thanks to Bjarne, Carl, and Dave for spending over an hour to make conversation in real time. The topics naturally evolved out of the random and it was an honor to be in the room with such wonderful people who've had such a huge impact on programming.

Tune in. Enjoy.

Embed

Format

Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image
      tertl3

      cool post, glad i found it in such a timely manner.  cant wait to get my 100 core intel for christmas :P

    • User profile image
      tentity

      My solution to 1000 cores is "automatic parallel computing" on parallect.codeplex.com.

      I use it for a couple of years and really enjoy it.

    • User profile image
      petke

      Very interesting talk. It was also entertaining as there was a bit of drama in there. Where disagreements where taken a bit personally at times.

    • User profile image
      Fabio Galuppo

      Great conversation!

    • User profile image
      sandramoebel

      This sounds like a great conversation - I'm ready to take lots of notes :)

    • User profile image
      Barony

      @Fabio Galuppo:To my mind one of the larger problems is figuring out which exposed functions are supposed to be part of the interface and which were simply pulled in because the header file happened to #include a file to get access to a struct or something. In C++ this is especially bad, because a class's definition may have been inlined, so it would need access to things that otherwise would never go in the header. Of course, #include is transitive, because you have to preprocess everything in each included header. Sometimes the API is supposed to expose functions pulled in from other headers, and sometimes it isn't.

    • User profile image
      Andrey Popandopulo

      Bjarne's motivation is nice and very creative!

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.