Herb Sutter's guest appearances

Herb Sutter

Hanselminutes with Scott Hanselman

CppCast

Going Deep (HD) - Channel 9

Lang.NEXT 2012 Sessions (HD)

GoingNative 2012 Sessions (HD)

Andrei Alexandrescu

Bjarne Stroustrup

Andrew Arnott

Lars Bak

Nikolai Tillmann

Eugene Sandulenko

Scott Meyers

Anders Hejlsberg

Patricia Aas

Tara Raj

Arlan Hamilton

Donald Glover

Sarah Cooper

Scott Adams

Daniel José

OwlTail

Herb Sutter joins Phil and Timur. We catch up on the news about LLVM 16 being released, a new book on initialisation in C++ and a couple of new user groups. Then we talk to Herb about his new language/ alternate syntax, Cpp2, which compiles down to C++ in much the same way that C with Classes compiled down to C.        News  LLVM 16.0.0 released "C++ initialisation story" - a new book by Bartlomiej Filipek New user group forming in Prague - Miloš Anđelković New user group forming in Helsinki - Timur Doumler  Links  CppFront - the compiler for Cpp2 "Can C++ be 10x Simpler &amp; Safer?" - Herb's CppCon keynote introducing Cpp2 and CppFront

Herb Sutter joins Phil and Timur. We catch up on the news about LLVM 16 being released, a new book on initialisation in C++ and a couple of new user groups. Then we talk to Herb about his new language/ alternate syntax, Cpp2, which compiles down to C++ in much the same way that C with Classes compiled down to C. <h3>News</h3> <ul> <li><a href="https://discourse.llvm.org/t/llvm-16-0-0-release/69326" rel="nofollow" target="_blank">LLVM 16.0.0 released</a></li> <li><a href="https://www.cppstories.com/2023/init-story-print/" rel="nofollow" target="_blank">"C++ initialisation story" - a new book by Bartlomiej Filipek</a></li> <li><a href="https://www.linkedin.com/posts/miloš-anđelković-79952118a_join-the-cppprague-discord-server-activity-7039505564371927040-K5AB/" rel="nofollow" target="_blank">New user group forming in Prague - Miloš Anđelković</a></li> <li><a href="https://www.meetup.com/cpphelsinki/" rel="nofollow" target="_blank">New user group forming in Helsinki - Timur Doumler</a></li> </ul> <h3>Links</h3> <ul> <li><a href="https://github.com/hsutter/cppfront" rel="nofollow" target="_blank">CppFront - the compiler for Cpp2</a></li> <li><a href="https://www.youtube.com/watch?v=ELeZAKCN4tY" rel="nofollow" target="_blank">"Can C++ be 10x Simpler &amp; Safer?" - Herb's CppCon keynote introducing Cpp2 and CppFront</a></li></ul>

Cpp2, with Herb Sutter

Rob and Jason are joined by Herb Sutter to discuss C++20 and some of his proposals that aim to Simplify C++.        Herb Sutter is an author, chair of the ISO C++ committee, and a systems languages architect at Microsoft. News  No one knows the type of char + char C++ Now 2019 Trip Report, Extension Points and Summer Opportunities JSON Link  Herb Sutter  @herbsutter Herb Sutter's GitHub Sutter's Mill  Links  P1000 - C++ IS Schedule P1185 - &lt;=&gt; != == P1186 - When do you actually use &lt;=&gt; Keynote: De-fragmenting C++: Making exceptions more affordable and usable - Herb Sutter CppCon 2018: Herb Sutter "Thoughts on a more powerful and simpler C++ (5 of N) C++ Coding Standars: 101 Rules, Guidelines, and Best Practices  Sponsors  PVS-Studio Facebook PVS-Studio Telegram  PVS-Studio Twitter   JetBrains   Hosts  @robwirving @lefticus

Rob and Jason are joined by Herb Sutter to discuss C++20 and some of his proposals that aim to Simplify C++. Herb Sutter is an author, chair of the ISO C++ committee, and a systems languages architect at Microsoft. <h3>News</h3> <ul> <li><a href="https://blog.knatten.org/2019/05/24/no-one-knows-the-type-of-char-char/" rel="nofollow" target="_blank">No one knows the type of char + char</a></li> <li><a href="https://thephd.github.io/c++now-2019-trip-report" rel="nofollow" target="_blank">C++ Now 2019 Trip Report, Extension Points and Summer Opportunities</a></li> <li><a href="https://github.com/beached/daw_json_link" rel="nofollow" target="_blank">JSON Link</a></li> </ul> <h3>Herb Sutter</h3> <ul> <li><a href="https://twitter.com/herbsutter" rel="nofollow" target="_blank">@herbsutter</a></li> <li><a href="https://github.com/hsutter" rel="nofollow" target="_blank">Herb Sutter's GitHub</a></li> <li><a href="https://herbsutter.com/" rel="nofollow" target="_blank">Sutter's Mill</a></li> </ul> <h3>Links</h3> <ul> <li><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1000r1.pdf" rel="nofollow" target="_blank">P1000 - C++ IS Schedule</a></li> <li><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1185r1.html" rel="nofollow" target="_blank">P1185 - &lt;=&gt; != ==</a></li> <li><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1186r1.html" rel="nofollow" target="_blank">P1186 - When do you actually use &lt;=&gt;</a></li> <li><a href="https://www.youtube.com/watch?v=os7cqJ5qlzo" rel="nofollow" target="_blank">Keynote: De-fragmenting C++: Making exceptions more affordable and usable - Herb Sutter</a></li> <li><a href="https://www.youtube.com/watch?v=80BZxujhY38" rel="nofollow" target="_blank">CppCon 2018: Herb Sutter "Thoughts on a more powerful and simpler C++ (5 of N)</a></li> <li><a href="https://amzn.to/2Iesl1U" rel="nofollow" target="_blank">C++ Coding Standars: 101 Rules, Guidelines, and Best Practices</a></li> </ul> <h3>Sponsors</h3> <ul> <li><a href="https://www.facebook.com/StaticCodeAnalyzer/" rel="nofollow" target="_blank">PVS-Studio Facebook</a></li> <li><a href="https://t.me/pvsstudio_en" rel="nofollow" target="_blank">PVS-Studio Telegram</a></li> <li> <a href="https://twitter.com/Code_Analysis" rel="nofollow" target="_blank">PVS-Studio Twitter</a> </li> <li> <a href="https://www.jetbrains.com/cpp/?utm_source=cppcast&amp;utm_medium=podcast&amp;utm_content=cppcast-podcast&amp;utm_campaign=cpp" rel="nofollow" target="_blank">JetBrains</a> </li> </ul> <h3>Hosts</h3> <ul> <li><a href="https://twitter.com/robwirving" rel="nofollow" target="_blank">@robwirving</a></li> <li><a href="https://twitter.com/lefticus" rel="nofollow" target="_blank">@lefticus</a></li></ul>

Simplifying C++

Rob and Jason are joined by Herb Sutter, chair of the ISO C++ standards committee to discuss the latest progress on C++ 17 made at the Oulu ISO Standards meeting.        Herb Sutter is a leading authority on software development. He is the best selling author of several books including Exceptional C++ and C++ Coding Standards, as well as hundreds of technical papers and articles, including the essay “The Free Lunch Is Over” which coined the term “concurrency revolution” and its recent sequel “Welcome to the Jungle” on the end of Moore’s Law and the turn to mainstream heterogeneous supercomputing from the cloud to ‘smartphones.’ Herb has served for a decade as chair of the ISO C++ standards committee, and is a software architect at Microsoft where he has led the language extensions design of C++/CLI, C++/CX, C++ AMP, and other technologies. News  The ANTLR4 C++ target is here Jon Kalb speaks about CppCon, C++17 standard and C++ community Meeting C++ 2016 Talks  Herb Sutter  @herbsutter Sutter's Mill  Links  What the ISO C++ committee added to the C++17 working draft at the Oulu 2016 meeting Last chance for CppCon 2016 Early Bird Registration!  Sponsor  Incredibuild

Rob and Jason are joined by Herb Sutter, chair of the ISO C++ standards committee to discuss the latest progress on C++ 17 made at the Oulu ISO Standards meeting. Herb Sutter is a leading authority on software development. He is the best selling author of several books including Exceptional C++ and C++ Coding Standards, as well as hundreds of technical papers and articles, including the essay “The Free Lunch Is Over” which coined the term “concurrency revolution” and its recent sequel “Welcome to the Jungle” on the end of Moore’s Law and the turn to mainstream heterogeneous supercomputing from the cloud to ‘smartphones.’ Herb has served for a decade as chair of the ISO C++ standards committee, and is a software architect at Microsoft where he has led the language extensions design of C++/CLI, C++/CX, C++ AMP, and other technologies. <h3>News</h3> <ul> <li><a href="http://www.soft-gems.net/index.php/tools/49-the-antlr4-c-target-is-here" rel="nofollow" target="_blank">The ANTLR4 C++ target is here</a></li> <li><a href="https://blog.jetbrains.com/clion/2016/06/jon-kalb-speaks-about-cppcon-cpp17-and-cpp-community/" rel="nofollow" target="_blank">Jon Kalb speaks about CppCon, C++17 standard and C++ community</a></li> <li><a href="http://meetingcpp.com/index.php/talks16.html" rel="nofollow" target="_blank">Meeting C++ 2016 Talks</a></li> </ul> <h3>Herb Sutter</h3> <ul> <li><a href="https://twitter.com/herbsutter" rel="nofollow" target="_blank">@herbsutter</a></li> <li><a href="https://herbsutter.com/" rel="nofollow" target="_blank">Sutter's Mill</a></li> </ul> <h3>Links</h3> <ul> <li><a href="https://www.reddit.com/r/cpp/comments/4pmlpz/what_the_iso_c_committee_added_to_the_c17_working/" rel="nofollow" target="_blank">What the ISO C++ committee added to the C++17 working draft at the Oulu 2016 meeting</a></li> <li><a href="http://cppcon.org/regopen2016/" rel="nofollow" target="_blank">Last chance for CppCon 2016 Early Bird Registration!</a></li> </ul> <h3>Sponsor</h3> <ul> <li><a href="https://www.incredibuild.com/cppoffer" rel="nofollow" target="_blank">Incredibuild</a></li></ul>

Oulu Trip Report

Herb Sutter presents atomic&lt;&gt; Weapons, 2 of 2. This was filmed at C++ and Beyond 2012. As the title suggests, this is a two part series (given the depth of treatment and complexity of the subject matter). STOP! =&gt; Watch part 1 first!Download the slides.Abstract:This session in one word: Deep.It's a session that includes topics I've publicly said for years is Stuff You Shouldn't Need To Know and I Just Won't Teach, but it's becoming achingly clear that people do need to know about it. Achingly, heartbreakingly clear, because some hardware incents you to pull out the big guns to achieve top performance, and C++ programmers just are so addicted to full performance that they'll reach for the big red levers with the flashing warning lights. Since we can't keep people from pulling the big red levers, we'd better document the A to Z of what the levers actually do, so that people don't SCRAM unless they really, really, really meant to.Topics Covered:The facts: The C++11 memory model and what it requires you to do to make sure your code is correct and stays correct. We'll include clear answers to several FAQs: "how do the compiler and hardware cooperate to remember how to respect these rules?", "what is a race condition?", and the ageless one-hand-clapping question "how is a race condition like a debugger?"The tools: The deep interrelationships and fundamental tradeoffs among mutexes, atomics, and fences/barriers. I'll try to convince you why standalone memory barriers are bad, and why barriers should always be associated with a specific load or store.The unspeakables: I'll grudgingly and reluctantly talk about the Thing I Said I'd Never Teach That Programmers Should Never Need To Now: relaxed atomics. Don't use them! If you can avoid it. But here's what you need to know, even though it would be nice if you didn't need to know it.The rapidly-changing hardware reality: How locks and atomics map to hardware instructions on ARM and x86/x64, and throw in POWER and Itanium for good measure – and I'll cover how and why the answers are actually different last year and this year, and how they will likely be different again a few years from now. We'll cover how the latest CPU and GPU hardware memory models are rapidly evolving, and how this directly affects C++ programmers.

Herb Sutter presents atomic&lt;&gt; Weapons, 2 of 2. This was filmed at <a href="http://cppandbeyond.com" rel="nofollow" target="_blank">C++ and Beyond 2012</a>. As the title suggests, this is a two part series (given the depth of treatment and complexity of the subject matter). STOP! =&gt; <a href="https://channel9.msdn.com/Shows/Going+Deep/Cpp-and-Beyond-2012-Herb-Sutter-atomic-Weapons-1-of-2" rel="nofollow" target="_blank">Watch part 1 first</a>!<a href="https://1drv.ms/b/s!Aq0V7yDPsIZOgcI0y2P8R-VifbnTtw" rel="nofollow" target="_blank">Download the slides</a>.Abstract:This session in one word: Deep.It's a session that includes topics I've publicly said for years is Stuff You Shouldn't Need To Know and I Just Won't Teach, but it's becoming achingly clear that people do need to know about it. Achingly, heartbreakingly clear, because some hardware incents you to pull out the big guns to achieve top performance, and C++ programmers just are so addicted to full performance that they'll reach for the big red levers with the flashing warning lights. Since we can't keep people from pulling the big red levers, we'd better document the A to Z of what the levers actually do, so that people don't <a href="http://en.wikipedia.org/wiki/Scram" rel="nofollow" target="_blank">SCRAM</a> unless they really, really, really meant to.Topics Covered:<ul><li>The facts: The C++11 memory model and what it requires you to do to make sure your code is correct and stays correct. We'll include clear answers to several FAQs: "how do the compiler and hardware cooperate to remember how to respect these rules?", "what is a race condition?", and the ageless one-hand-clapping question "how is a race condition like a debugger?"</li><li>The tools: The deep interrelationships and fundamental tradeoffs among mutexes, atomics, and fences/barriers. I'll try to convince you why standalone memory barriers are bad, and why barriers should always be associated with a specific load or store.</li><li>The unspeakables: I'll grudgingly and reluctantly talk about the Thing I Said I'd Never Teach That Programmers Should Never Need To Now: relaxed atomics. Don't use them! If you can avoid it. But here's what you need to know, even though it would be nice if you didn't need to know it.</li><li>The rapidly-changing hardware reality: How locks and atomics map to hardware instructions on ARM and x86/x64, and throw in POWER and Itanium for good measure – and I'll cover how and why the answers are actually different last year and this year, and how they will likely be different again a few years from now. We'll cover how the latest CPU and GPU hardware memory models are rapidly evolving, and how this directly affects C++ programmers.</li></ul>

C++ and Beyond 2012: Herb Sutter - atomic&lt;&gt; Weapons, 2 of 2

Herb Sutter presents atomic&lt;&gt; Weapons, 1 of 2. This was filmed at C++ and Beyond 2012. As the title suggests, this is a two part series (given the depth of treatment and complexity of the subject matter).Part 1 -&gt; Optimizations, races, and the memory model; acquire and release ordering; mutexes vs. atomics vs. fencesDownload the slides.Abstract:This session in one word: Deep.It's a session that includes topics I've publicly said for years is Stuff You Shouldn't Need To Know and I Just Won't Teach, but it's becoming achingly clear that people do need to know about it. Achingly, heartbreakingly clear, because some hardware incents you to pull out the big guns to achieve top performance, and C++ programmers just are so addicted to full performance that they'll reach for the big red levers with the flashing warning lights. Since we can't keep people from pulling the big red levers, we'd better document the A to Z of what the levers actually do, so that people don't SCRAM unless they really, really, really meant to.Topics Covered:The facts: The C++11 memory model and what it requires you to do to make sure your code is correct and stays correct. We'll include clear answers to several FAQs: "how do the compiler and hardware cooperate to remember how to respect these rules?", "what is a race condition?", and the ageless one-hand-clapping question "how is a race condition like a debugger?"The tools: The deep interrelationships and fundamental tradeoffs among mutexes, atomics, and fences/barriers. I'll try to convince you why standalone memory barriers are bad, and why barriers should always be associated with a specific load or store.The unspeakables: I'll grudgingly and reluctantly talk about the Thing I Said I'd Never Teach That Programmers Should Never Need To Now: relaxed atomics. Don't use them! If you can avoid it. But here's what you need to know, even though it would be nice if you didn't need to know it.The rapidly-changing hardware reality: How locks and atomics map to hardware instructions on ARM and x86/x64, and throw in POWER and Itanium for good measure – and I'll cover how and why the answers are actually different last year and this year, and how they will likely be different again a few years from now. We'll cover how the latest CPU and GPU hardware memory models are rapidly evolving, and how this directly affects C++ programmers.Part 2 -&gt; Restrictions on compilers and hardware (incl. common bugs); code generation and performance on x86/x64, IA64, POWER, ARM, and more; relaxed atomics; volatile

Herb Sutter presents atomic&lt;&gt; Weapons, 1 of 2. This was filmed at <a href="http://cppandbeyond.com" rel="nofollow" target="_blank">C++ and Beyond 2012</a>. As the title suggests, this is a two part series (given the depth of treatment and complexity of the subject matter).Part 1 -&gt; Optimizations, races, and the memory model; acquire and release ordering; mutexes vs. atomics vs. fences<a href="https://1drv.ms/b/s!Aq0V7yDPsIZOgcI0y2P8R-VifbnTtw" rel="nofollow" target="_blank">Download the slides</a>.Abstract:This session in one word: Deep.It's a session that includes topics I've publicly said for years is Stuff You Shouldn't Need To Know and I Just Won't Teach, but it's becoming achingly clear that people do need to know about it. Achingly, heartbreakingly clear, because some hardware incents you to pull out the big guns to achieve top performance, and C++ programmers just are so addicted to full performance that they'll reach for the big red levers with the flashing warning lights. Since we can't keep people from pulling the big red levers, we'd better document the A to Z of what the levers actually do, so that people don't <a href="http://en.wikipedia.org/wiki/Scram" rel="nofollow" target="_blank">SCRAM</a> unless they really, really, really meant to.Topics Covered:<ul><li>The facts: The C++11 memory model and what it requires you to do to make sure your code is correct and stays correct. We'll include clear answers to several FAQs: "how do the compiler and hardware cooperate to remember how to respect these rules?", "what is a race condition?", and the ageless one-hand-clapping question "how is a race condition like a debugger?"</li><li>The tools: The deep interrelationships and fundamental tradeoffs among mutexes, atomics, and fences/barriers. I'll try to convince you why standalone memory barriers are bad, and why barriers should always be associated with a specific load or store.</li><li>The unspeakables: I'll grudgingly and reluctantly talk about the Thing I Said I'd Never Teach That Programmers Should Never Need To Now: relaxed atomics. Don't use them! If you can avoid it. But here's what you need to know, even though it would be nice if you didn't need to know it.</li><li>The rapidly-changing hardware reality: How locks and atomics map to hardware instructions on ARM and x86/x64, and throw in POWER and Itanium for good measure – and I'll cover how and why the answers are actually different last year and this year, and how they will likely be different again a few years from now. We'll cover how the latest CPU and GPU hardware memory models are rapidly evolving, and how this directly affects C++ programmers.</li></ul>Part 2 -&gt; <a href="https://channel9.msdn.com/Shows/Going+Deep/Cpp-and-Beyond-2012-Herb-Sutter-atomic-Weapons-2-of-2" rel="nofollow" target="_blank">Restrictions on compilers and hardware (incl. common bugs); code generation and performance on x86/x64, IA64, POWER, ARM, and more; relaxed atomics; volatile</a>

C++ and Beyond 2012: Herb Sutter - atomic&lt;&gt; Weapons, 1 of 2

Herb Sutter presents C++ Concurrency. This was filmed at C++ and Beyond 2012.Get Herb's slides for this session.Herb says:I've spoken and written on these topics before. Here's what's different about this talk:Brand new: This material goes beyond what I've written and taught about before in my Effective Concurrency articles and courses. Cutting-edge current: It covers the best-practices state of the art techniques and shipping tools, and what parts of that are standardized in C++11 already (the answer to that one may surprise you!) and what's en route to near-term standardization and why, with coverage of the latest discussions. Blocking vs. non-blocking: What's the difference between blocking and non-blocking styles, why on earth would you care, which kinds does C++11 support, and how are we looking at rounding it out in C++1y? The answers all matter to you – even the ones not yet in the C++ standard – because they are real, available in shipping products, and affect how you design your software today.

Herb Sutter presents C++ Concurrency. This was filmed at <a href="http://cppandbeyond.com" rel="nofollow" target="_blank">C++ and Beyond 2012</a>.<a href="http://sdrv.ms/ZJ4EEk" rel="nofollow" target="_blank">Get Herb's slides </a>for this session.Herb says:I've spoken and written on these topics before. Here's what's different about this talk:<ul><li>Brand new: This material goes beyond what I've written and taught about before in my Effective Concurrency articles and courses. </li><li>Cutting-edge current: It covers the best-practices state of the art techniques and shipping tools, and what parts of that are standardized in C++11 already (the answer to that one may surprise you!) and what's en route to near-term standardization and why, with coverage of the latest discussions. </li><li>Blocking vs. non-blocking: What's the difference between blocking and non-blocking styles, why on earth would you care, which kinds does C++11 support, and how are we looking at rounding it out in C++1y? </li></ul>The answers all matter to you – even the ones not yet in the C++ standard – because they are real, available in shipping products, and affect how you design your software today.

C++ and Beyond 2012: Herb Sutter - C++ Concurrency

The world runs on C and C++. Did you know that? Herb Sutter sits down to convince Scott that he's not only standing on the shoulders of giants but that those giants all write C++.

The world runs on C and C++. Did you know that? Herb Sutter sits down to convince Scott that he's not only standing on the shoulders of giants but that those giants all write C++.

Why C++ with Herb Sutter

What makes ISO C++11 "feel like a new language"? What things that we know about past C++ do we need to unlearn? Why is C++ designed the way it is – historically, and in C++11? Finally, what is the difference between managed and native languages anyway, and when is each applicable? This talk gives an overview and motivation of modern C++ and why it's clean, safe, and fast – as clean to code in and as type-safe as any modern language, and more than ever the king of "fast."

What makes ISO C++11 "feel like a new language"? What things that we know about past C++ do we need to unlearn? Why is C++ designed the way it is – historically, and in C++11? Finally, what is the difference between managed and native languages anyway, and when is each applicable? This talk gives an overview and motivation of modern C++ and why it's clean, safe, and fast – as clean to code in and as type-safe as any modern language, and more than ever the king of "fast."

Herb Sutter: (Not Your Father’s) C++

This talk will cover:Which key features in C++11 will most change the way you write code: the features that directly affect C++ style, coding idioms, and the guidance in pre-C++11 books and articles that most needs to be updated. Specific guidance on each of those key features: how each one changes your code; tips on using it well; and a pitfall or two to avoid (and how). Status update on C++11 adoption: how compilers, books, and programmers are doing, plus a few updates and projections. What's next for C++: what's top of mind for the near future of Standard C++, and why? 

This talk will cover: <ul><li>Which key features in C++11 will most change the way you write code: the features that directly affect C++ style, coding idioms, and the guidance in pre-C++11 books and articles that most needs to be updated. </li><li>Specific guidance on each of those key features: how each one changes your code; tips on using it well; and a pitfall or two to avoid (and how). </li><li>Status update on C++11 adoption: how compilers, books, and programmers are doing, plus a few updates and projections. </li><li>What's next for C++: what's top of mind for the near future of Standard C++, and why? </li></ul>