Reading this causes me to experience déjà vu; years and years of reading stories and watching presentations about someone struggling with GC in the JVM. It's happening all over again with Go. The same 'discoveries', the same trade-offs, the same discussions about hardware resources, the same 'concurrent mark and sweep', the same 'more to do' conclusions. You could replace every occurrence of 'Go' with 'Java' and it would probably go undiscovered.
Maybe it's all worth it and this is how developers are supposed to spend their time, but it's no longer interesting to me.
Maybe it's all worth it and this is how developers are supposed to spend their time, but it's no longer interesting to me.