Media Summary: The world runs on C++. For more than two decades, C++ has served as the workhorse of high-performance, low-power, and ... Programming Much has been said about how the upcoming module feature in C++ will improve compilation ... Are memory allocators really worth the trouble? What situations merit their use? How are they applied effectively? What's the ...

Code Dive 2017 John Lakos - Detailed Analysis & Overview

The world runs on C++. For more than two decades, C++ has served as the workhorse of high-performance, low-power, and ... Programming Much has been said about how the upcoming module feature in C++ will improve compilation ... Are memory allocators really worth the trouble? What situations merit their use? How are they applied effectively? What's the ... Interested in large‑scale C++ design done right?

Photo Gallery

code::dive 2017 – John Lakos – Local (“arena”) memory allocator
code::dive 2017 – John Lakos – Value semantics: It ain't about the syntax!
CppCon 2017: John Lakos “Local ('Arena') Memory Allocators (part 1 of 2)”
What C++ Needs to be Safe | John Lakos | Stage 1
CppCon 2017: John Lakos “Local ('Arena') Memory Allocators (part 2 of 2)”
C++Now 2017: John Lakos "Local (“Arena”) Memory Allocators"
C++Now 2018: John Lakos “C++ Modules & Large-Scale Development”
code::dive 2017 live stream, day 1, stage 1
John Lakos - Boundary Conditions - Secret Lightning Talks -  Meeting C++ 2017
C++ Modules and Large-Scale Development - John Lakos [ACCU 2019]
CppCon 2014: John Lakos "Defensive Programming Done Right, Part I"
Local (Arena) Memory Allocators Part 1 - John Lakos - Meeting C++ 2017
View Detailed Profile
code::dive 2017 – John Lakos – Local (“arena”) memory allocator

code::dive 2017 – John Lakos – Local (“arena”) memory allocator

Let's welcome

code::dive 2017 – John Lakos – Value semantics: It ain't about the syntax!

code::dive 2017 – John Lakos – Value semantics: It ain't about the syntax!

The first speaker of today is

CppCon 2017: John Lakos “Local ('Arena') Memory Allocators (part 1 of 2)”

CppCon 2017: John Lakos “Local ('Arena') Memory Allocators (part 1 of 2)”

http://CppCon.org — Presentation Slides, PDFs, Source

What C++ Needs to be Safe | John Lakos | Stage 1

What C++ Needs to be Safe | John Lakos | Stage 1

The world runs on C++. For more than two decades, C++ has served as the workhorse of high-performance, low-power, and ...

CppCon 2017: John Lakos “Local ('Arena') Memory Allocators (part 2 of 2)”

CppCon 2017: John Lakos “Local ('Arena') Memory Allocators (part 2 of 2)”

http://CppCon.org — Presentation Slides, PDFs, Source

C++Now 2017: John Lakos "Local (“Arena”) Memory Allocators"

C++Now 2017: John Lakos "Local (“Arena”) Memory Allocators"

http://cppnow.org — Presentation Slides, PDFs, Source

C++Now 2018: John Lakos “C++ Modules & Large-Scale Development”

C++Now 2018: John Lakos “C++ Modules & Large-Scale Development”

http://cppnow.org — Presentation Slides, PDFs, Source

code::dive 2017 live stream, day 1, stage 1

code::dive 2017 live stream, day 1, stage 1

Logical versus Physical Design ...

John Lakos - Boundary Conditions - Secret Lightning Talks -  Meeting C++ 2017

John Lakos - Boundary Conditions - Secret Lightning Talks - Meeting C++ 2017

Meeting C++

C++ Modules and Large-Scale Development - John Lakos [ACCU 2019]

C++ Modules and Large-Scale Development - John Lakos [ACCU 2019]

Programming #Cpp #AccuConf Much has been said about how the upcoming module feature in C++ will improve compilation ...

CppCon 2014: John Lakos "Defensive Programming Done Right, Part I"

CppCon 2014: John Lakos "Defensive Programming Done Right, Part I"

http://www.cppcon.org — Presentation Slides, PDFs, Source

Local (Arena) Memory Allocators Part 1 - John Lakos - Meeting C++ 2017

Local (Arena) Memory Allocators Part 1 - John Lakos - Meeting C++ 2017

Are memory allocators really worth the trouble? What situations merit their use? How are they applied effectively? What's the ...

John Lakos - code::dive 2025 interview

John Lakos - code::dive 2025 interview

Interested in large‑scale C++ design done right?