I've written production C++ code for > 10 years, and I would definitely prefer to use Go for a lot of programs. Yes, it might be slower for some use-cases, it h

I've written production C++ code for > 10 years, and I would definitely prefer to use Go for a lot of programs. Yes, it might be slower for some use-cases, it has some ugly parts. But it's also orders of magnitude easier to understand and the ability to just focus on the actual problem statement and build a solution instead of nerding out over language features is nice. I'm definitely not enjoying reverse engineering some smart SFINAE code, and writing any networking code with asio is also no longer very high on my "love to do things" list. I would rather deal with a few "if (err != nil) { return nil, err; }" statements. But maybe it just depends on what "true C++ coders" means. If it's C++ enthusiasts for the sake of loving the language, I'm sure you are right. If it's "C++ users", because that was 10 years ago the best tool to solve a certain set of problems and the jobs where mostly C++, there's likely a few who are open to other tools to solve their problems. That said I'm