All of this without even getting into Rob Pike (the man largely responsible for its origin, if you're not familiar) saying explicitly it was for people who weren't capable of understanding a better language:
«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, 2014.
Go is a fine language, but let's not pretend, here. Rob Pike certainly doesn't.
As a C# developer, I get to deal with a lot more:
- Bikeshedding over LINQ
- Going back and optimizing LINQ
- Helping Developers understand someone else's LINQ, Reflection/Attribute Abuse
- Helping developers understand new syntax in each version of the language.
A large part of Go's philosophy is to more or less take away all of those tools from the Developer and try to force a style of code that is somewhat monotonous, verbose (in a way very different from Java), yet 'readable' by a developer with minimal experience.
The same is more or less true of Go. Abstractions can be bad, but in the majority of cases it is the only tool we have against complexity, and a method with an annotation may be thousands time more readable/understandable than the reimplementation of a given identical functionality for the thousands time.
Go is inferior (to me) because it doesn't have s-expressions, and it doesn't offer interactive development (who in the world wants to re-compile/re-run a whole program/tests on each change?).
Once you've got the taste for interactive development it's really hard to go back to anything else. Ask any Smalltalk developer what they think of other languages.
So my move.
1. Common Lisp (well obviously) 2. Racket (gotta make some noise) 3. Haskell (controversial, I know) 4. Rust (trendy and deservedly) 5. APL (terseness) 6. Prolog (made me think differently) 7. Fortran (come a long way) 8. Forth (brevity) 9. Ada (correctness) 10. Lean (I really like Lean) . . C . . C++ . . Python . Perl . Shell . . ECMAscript
Is there anyone I haven't offended? Do let me know :)
"A Critical Analysis of String APIs: the Case of Pharo" https://hal.inria.fr/hal-01651250/document
----
For CRUD stuff, PHP & Notepad will probably be OK.
For other stuff, local type inference does make a difference.
So does the widespread availability of free-as-in-beer source code libraries.