It sounds like you are operating in an existing org with a mature codebase. In this context, where the existing product is implemented using C++, continuing to

It sounds like you are operating in an existing org with a mature codebase. In this context, where the existing product is implemented using C++, continuing to use the language makes perfect sense. I implement and maintain C++ for my day job so sure, it's not that bad ... it's only bad when you compare it to the state of the art in other language ecosystems. "This isn't rocket science. Could it be easier? Sure. But it's not terrible either." I don't know how to measure "terrible". I agree it's not rocket science. And it's much better than two decades ago. But still, compared almost to any other industrial language (which of course have their own set of problems) the default experience setting up and maintaining a cross platform project is abysmal. By "abysmal" I mean that defining the build is not a project goal in itself that requires meticulous design and expertise, and is something that just works out of the box. If you work only in posix land the experience is far less uncomfortable, of course.