> Eventually Go will also reach a point where it will start lagging and then some smart engineer will conclude that you need to switch to C++! Go is much bette

> Eventually Go will also reach a point where it will start lagging and then some smart engineer will conclude that you need to switch to C++! Go is much better suited for large codebases than Node.js though, so when it becomes bloated again, it'll be easier to fix problems with/optimize the existing code and rewrites can be avoided.