The Badlands of C++: Professional Game Development
summary
Game studios standardize on Visual Studio-driven toolchains, avoid STL where allocators and compile bloat hurt tight budgets, and sometimes replace it with EA’s EASTL or hand-rolled containers like intrusive containers and fixed vectors to control memory and performance. Production builds hit millions of lines (examples around 10M LOC) and nightly or distributed builds still take 15–60 minutes. Error handling favors no exceptions on hot paths, reflection comes from code-generation annotations (Unreal-style property metadata) rather than runtime RTTI.
AI-written summary · about
chapters (6)
related talks
57mThis Videogame Programmer Used the STL and You Will Never Guess What Happened Next
58mMemory and C++ debugging at Electronic Arts
01h 22mC++ ecosystem: For better, for worse
53mStandard C++ Toolset
01h 06mModern C and What We Can Learn From It
57mC++ MythBusters Strike 2
42mThe Hidden Side of the Pixel
01h 31mClean(er) Code for Large Scale Legacy Applications