Earlier quoted context omitted.
It's interesting how the introduction of "modules" has forced so many to stick with C++17 and Java 8.
C++ has barely any feature complete compiler implementations and build systems aren’t ready for all of its additions, either (CMake and modules in particular). libstdc++ and libc++, gcc and clang are all not ready for production use or rather untested and/or buggy. Unless you’re targeting MSBuild Visual Studio Solutions and Windows only, C++17 is currently the most up to date, stable, and battle-proven version.
Which items from this table are lying about GCC v11 support of C++20? [1] Which of the features are buggy in GCC v11-12?
[1] https://en.cppreference.com/w/cpp/compiler_support#cpp20