[bdamm]

Since I've been working in C++ a lot recently I decided to watch the video as I waited for a build to complete. So the length is about right. And fortunately, the video is a delight!

[zeafoamrun]

I have read as much as I can on the history of C++ and I'm looking forward to watch this. I find the process of it's evolution deeply fascinating.

[tonyedgecombe]

I feel drawn to watch it in the same way I was drawn to watch Breaking Bad.

[abcd_f]

> the process of it's (sic) evolution deeply fascinating.

... as it is disappointing.

Not everything that can be done should be done.

[stackghost]

Wow is this just a shitpost (it was funny!) or do your builds actually take about an hour? That's nuts, if so.

[wavemode]

A fresh build of a large C++ project taking 1 hour does not sound strange at all.

If that's an incremental build though (i.e. simply rebuilding after changing a few files), there's something very wrong.

[darknavi]

FASTBuild has been a game changer for our team recently if you have extra hardware sitting around.

https://www.fastbuild.org/docs/home.html

[surajrmal]

Your org needs better distributed build caching if you can't get that number lower. All builds should be "incremental" with appropriate caching.

[wavemode]

Not everyone in the world who compiles a C++ project is necessarily doing so for an "org"

[account42]

It does if you have an even remotely reasonably specced development machine.

[bdamm]

Yes, although in all honesty the actual compilation is somewhat small compared to the many layers of unit, simulation, integration, and regression tests. All those corner cases take a long time to explore.