By shedding the heavy skin of the past, embracing Clang, integrating CMake, and pushing hard on standard conformance, Visual C++ 2017 brought the Windows development experience back into alignment with the global C++ community. It set the stage for the C++20 standard and proved that a decades-old toolset could evolve to meet the demands of modern systems programming.
// If you hear this, the brakes still work. visual c++ 2017
Perhaps the most experimental but high-impact feature introduced was the support for C++ Modules (initially proprietary, later aligning with the standard). C++ has historically suffered from the fragility and slowness of the #include preprocessor model. Modules promised to replace textual inclusion with a binary interface mechanism. In VS2017, Microsoft pioneered this by allowing developers to build ifc (Interface Files). This drastically reduced compilation times for large codebases, as the compiler no longer needed to parse the same header files thousands of times across different translation units. By shedding the heavy skin of the past,