2 ms·
There's always a tension between maintaining an existing codebase and trying something new but in that case I'd personally jump on a Go codebase instead of C/C+
by acdha 6y ago
There's always a tension between maintaining an existing codebase and trying something new but in that case I'd personally jump on a Go codebase instead of C/C++ in a heartbeat just for the maintainability improvements. There is a meaningful difference between “can a turing-complete language do this?” and “how much time will you spend dealing with avoidable problems or overhead?” and in the case of unsafe languages I find the arguments relatively compelling for picking anything safer to use in practice.