2 ms·

100% agree this is something that would have immediate, high value impact. The fact that building C++ is this opaque process defined in 15 different ways via m

100% agree this is something that would have immediate, high value impact. The fact that building C++ is this opaque process defined in 15 different ways via make, autoconf, automake, cmake, ninja, with 50 other toolchains is something that continues to create a barrier to entry. I still remember the horrors of trying to compile c++ in 2004 on windows without anything besides borland... Standardizing the build system and toolchain needs to happen. It's a hard problem that needs to be solved.

maccard 7mo ago
> Standardizing the build system and toolchain needs to happen. It's a hard problem that needs to be solved. I agree, and I also think it’s never happening. It requires agreeing on so many things that are subjective and likely change behaviour. C++ couldn’t even manage to get module names to be required to match the file name. That was for a new feature that would have allowed us to figure out esports without actually opening the file…