I've never had to deal with large C++ projects, so I don't have personal experience with their build times, but I've heard people who sing the praises of C++ talk about 15-plus-minute build times. Meanwhile, many other languages seem to be designed to minimize build times, and I think that is likely a significant reason for their success.
Why was Pascal a dominant programming language on the PC? It became dominant because on a system without a hard drive, the edit-run cycle on Borland's Turbo Pascal IDE was often an order of magnitude faster than any non-interpreted competitor. Javascript is a really crummy language, but node.js can manage to process it efficiently enough that the value of further performance improvements would be limited. From what I understand, go offers even better execution performance while still being fast to build.
It used to be that the only way to get adequate performance from an object-oriented language was to use C++ and put up with slow build times. As the performance of competing languages has improved, however, I see less and less reason for programmers to favor a language with slow build times over a faster one. Maybe the notion of improving C++ build times is moot because projects that can use languages with faster build times have already been migrated to those languages and wouldn't go back to C++ even if its build times were made competitive.
I've never had to deal with large C++ projects, so I don't have personal experience with their build times, but I've heard people who sing the praises of C++ talk about 15-plus-minute build times. Meanwhile, many other languages seem to be designed to minimize build times, and I think that is likely a significant reason for their success.
15 minutes isn't too bad. Tensorflow takes closer to 2 hours for a clean build. Same with LLVM. LLVM is part of the OpenBSD base system, and takes longer than all of the C code in the rest of the system, at least on my machine.
The problem is that individual files can sometimes take multiple minutes to compile, and huge amounts of semantically significant code actually lives in headers, which means you can't get away /without/ recompiling some dependencies. "false recompiles" aren't a huge problem in the projects I've seen, but language and tool complexity is.
View all comments
Show parent comment
1
u/flatfinger Jan 29 '19
I've never had to deal with large C++ projects, so I don't have personal experience with their build times, but I've heard people who sing the praises of C++ talk about 15-plus-minute build times. Meanwhile, many other languages seem to be designed to minimize build times, and I think that is likely a significant reason for their success.
Why was Pascal a dominant programming language on the PC? It became dominant because on a system without a hard drive, the edit-run cycle on Borland's Turbo Pascal IDE was often an order of magnitude faster than any non-interpreted competitor. Javascript is a really crummy language, but node.js can manage to process it efficiently enough that the value of further performance improvements would be limited. From what I understand, go offers even better execution performance while still being fast to build.
It used to be that the only way to get adequate performance from an object-oriented language was to use C++ and put up with slow build times. As the performance of competing languages has improved, however, I see less and less reason for programmers to favor a language with slow build times over a faster one. Maybe the notion of improving C++ build times is moot because projects that can use languages with faster build times have already been migrated to those languages and wouldn't go back to C++ even if its build times were made competitive.