> The language has memory-safe concurrency (except for maps, which is weird)... My understanding is you should operate the other way around. Things aren't safe

> The language has memory-safe concurrency (except for maps, which is weird)... My understanding is you should operate the other way around. Things aren't safe for concurrent mutation unless it's explicitly documented as safe. > So you can have parallelism without worrying too much about race conditions or leaks. You might not worry, but I find these the two easiest classes of Go bug to find when entering new codebases ;). Still, I agree Go is easier to get a web service up and running with.