emphasis on "easy concurrency", yet hardly simple. What C messed up with memory, Go seems to mess up with concurrency primitives. The ease with which you can introduce thread leaks and race conditions is just ridiculous.
Sure, they say use the race detector. But then I say: sure, but I need to run it first.
Of course the race detector isn't holy either. Thread leaks are a thing and there's probably a detector for that somewhere too. But surely the parallel to messing up memory with C and its detectors (valgrind?) can be made, and I thought we were all pretty done with that.
I never shot myself in the foot with Java and Scala as easily compared to go, yet you almost get ridiculed for mentioning those 2 former languages.
Sure, they say use the race detector. But then I say: sure, but I need to run it first.
Of course the race detector isn't holy either. Thread leaks are a thing and there's probably a detector for that somewhere too. But surely the parallel to messing up memory with C and its detectors (valgrind?) can be made, and I thought we were all pretty done with that.
I never shot myself in the foot with Java and Scala as easily compared to go, yet you almost get ridiculed for mentioning those 2 former languages.