From the start we've been building the language we want to use, ourselves. And we do use it and are happy to use it.
"You're too dumb" is absolutely not our attitude toward Go programmers. I would find that offensive too.
Also, if we really believed people were too dumb to understand these things I wouldn't have written so much text to try to bring people along for the decision. I'd have just put in the text I wanted and walked away.
Okay. Then I guess matter is just the wording then. I find the Rustonomicon warning much more inviting:
> Should you wish a long and happy career of writing Rust programs, you should turn back now and forget you ever saw this book. It is not necessary. However if you intend to write unsafe code—or just want to dig into the guts of the language—this book contains lots of useful information.
What I like: (1) the advice not to read this document is presented using the word "should," but in Go's case, the doc first presumes the reader as being too clever and then directly commands the reader not to be too clever; (2) the Rust version acknowledges a basic human trait that is curiosity, inviting those curious enough to explore the guts of the language to dig in, but the Go version does not.
I'm sure you have great intention, but can you acknowledge the wording comes across as off-putting and condescending?
"You're too dumb" is absolutely not our attitude toward Go programmers. I would find that offensive too.
Also, if we really believed people were too dumb to understand these things I wouldn't have written so much text to try to bring people along for the decision. I'd have just put in the text I wanted and walked away.