That is the most bloated boilerplate project I've ever seen. Does anyone actually use this for their projects? I would hope not. I know Javascript people are us

That is the most bloated boilerplate project I've ever seen. Does anyone actually use this for their projects? I would hope not. I know Javascript people are used to starting a project with a template/boilerplate, but that's not a good idea in C++ land. You actually need to understand the stack you're using, and all of the tools (unless you're working on a team, in which case that could be someone else's responsibility) Also, QT projects aren't real C++ since they require an additional preprocessor to compile custom syntax additions for "signals" and "slots". As a consequence, tooling for those projects tend to be more complicated and clunky. This linked project seems to be trying to stuff as many things as they possibly can into a hello world project. With Conan + CMake you only need like 3 files total in your entire project for something like this: * conanfile.txt: for declaring requirements/dependencies * CMakeLists.txt: describe how to compile your project * main.cpp: source code for the hello world app Also, > Yes, I realize CMake isn't modern and there are a bunch of new build tools. No!! That thinking is a trap. CMake is modern, and using something else is more likely to cause problems for you and anyone who might want to use your project. That boilerplate's is a bad example. A fully functional SDL2 hello world with Conan can be done with a ~4 LoC CMakeLists.txt. Unless you have a very good reason (there are good reasons, but they're the exception rather than the rule), don't build your C++ project with anything other than CMake.