|
|
|
|
|
by tptacek
4017 days ago
|
|
If this was true, and not a just-so story, then it should be easy to point to several well-known open source projects that started out in Golang and ended up in some other language, or several concepts that were prototyped in Golang and then ported over to some other language. Like every programming language ever, there are surely many Golang users who've used it solely to add a keyword to their resume. That's not a very interesting observation, because the same thing is true of Rust, Scala, and even Haskell. Further, that doesn't really address the question of why so many teams select Golang in the first place. A programmer might use Golang to get the keyword on their resume, but a team shipping a new product has no such incentive. |
|
I largely dislike Go but keep picking it because it is the lowest common denominator of languages my team will use and I really like them.
Even the proponents of Go on my team are moving away from it as their preferred choice, but for now it remains the only consensus fallback.