I was worried about that as well, but the change has been very positive. I've found modern C++ to be very productive to code in ('auto' and lambdas are huge) an

I was worried about that as well, but the change has been very positive. I've found modern C++ to be very productive to code in ('auto' and lambdas are huge) and the libraries I have direct access to now (vs. working through a compiled Node extension) have significantly improved my productivity relative to Node.js/TypeScript. I'm currently evaluating moving a few other codebases I've built from TypeScript to C++. The main thing that's made C++ work for us, though, has been embracing Bazel[0] as our build/package management system. I had no idea how big a difference that would make, but it's been huge and I would go so far as to say that without Bazel, we would have probably abandoned C++ (at least for our use cases). We do still have a few services that are still written in Node.js, but these are micro-services that use a vendor's Node.js library to call some API—typically < 100 LOC each. They connect to our C++ server over a WebSocket and we message them with JSON (currently) as needed. So we're not 100% C++ right now, but all of the primary logic is in C++ today. [0] http://bazel.io http://bazel.io