3 ms·
At this point, why not just use C++? I feel like people are trying to stretch Go way past what it's good for. It's not going to replace C++ where C++ is effecti
by brian-armstrong 9y ago
At this point, why not just use C++? I feel like people are trying to stretch Go way past what it's good for. It's not going to replace C++ where C++ is effective, and it shouldn't :)
- pcwalton 9y agoBecause memory safety is much easier to achieve in Go than in C++, even "modern C++".