> At least now the code that "seems to work" usually does, and is memory-safe now, so yes, it's an improvement. The most significant part of that statement com

> At least now the code that "seems to work" usually does, and is memory-safe now, so yes, it's an improvement. The most significant part of that statement comes from accepting contributions into your project. Java has made it much saner to just look at a patch and LGTM +1, over any work I've ever done in C/asm. Trust in the careful handling of memory by a stranger has been replaced by trust in the system to complain if they don't ... which has made for bigger and wider communities of strangers sending each other patches.