4 ms·
>The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe
by HideousKojima 1y ago
>The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt.
- Rob Pike
- lionkor 1y agoSo they made it easy to have data races in a language all about concurrency, bravo. Not buying it.
- ad_hockey 1y agoIt's possible to have data races if you ignore the language conventions[1]. But even then, Go has provided an effective data race detection tool since 1.1: https://go.dev/blog/race-detector https://go.dev/blog/race-detector I've been using Go on a large codebase for a number of years, and I haven't found data races to be a problem in practice. [1] https://go.dev/doc/effective_go#sharing https://go.dev/doc/effective_go#sharing
- lionkor 1y agoThat's fantastic, good job! "Just be good enough at your job" is why C++ is fully concurrency- and memory safe, too. But, you know, its not, that's not how juniors use it, and boy do they write a lot of codebases I end up maintaining.
- tyre 1y agosorry is the point here that enums are too complicated to understand?
- pjmlp 1y agoApparently, like most modern language features in the last 50 years or so.