Well erlang and go do have a virtual machine concept because they are basically flip off great big coroutine schedulers at the end of the day (or are they OS's

Well erlang and go do have a virtual machine concept because they are basically flip off great big coroutine schedulers at the end of the day (or are they OS's?). Go and erlang give nifty coroutine initialisation and communication stuff - that is all with language constructs on top. c++ has none so you're free to choose depending on what you need to do. It's a good general purpose language. Usability is perfectly fine when you consider C++11 and boost for example. They both can the useful abstractions. Transactional code is pretty easy. You can do it fine with closures you know, elegantly without resorting to metaprogramming monstrosities. Metaprogramming is a PITA in large systems from a maintenance perspective. Its not as masochistic as finding erlang developers. Nor is it all that masochistic actually if you consider the good old CSP paper and apply that to your code. The "enterprise outfit" nonsense is us large businesses who have a vacuum of quality staff because people would rather work at google (for a lesser salary I'll add) where they can take on menial duties and be kept away from the competition. We build really big, complicated systems like you've never seen with "inferior" tools, low quality staff, very little CPU time and not a mention of erlang or Go. In fact some of our shit is handling 1000 requests a second on VB6+DCOM. Go figure...