3 ms·
I started writing Go at age 23, for what its worth. (That was a just a few years ago.) I like Go because its simple. Obviously, that is also its downfall. Overa
by jchw 7y ago
I started writing Go at age 23, for what its worth. (That was a just a few years ago.) I like Go because its simple. Obviously, that is also its downfall. Overall, I would still hold it as one of the best languages for writing various kinds of software (servers, CLI tools, and some odds and ends.)
It’s true that you can write bad Go by trying to do things that are not a good idea, but I’m not sure what you’d expect. The Go ecosystem is damning evidence of the ease of writing pretty good code in the language.
Disclaimer: I work for Google (but I do not work on Go and I did not work for Google when I first began writing Go.)
- dnautics 7y agoNo doubt. I strongly believe go is a major advancement over c/c++ for routine work and an improvement over python. There are, however major footguns, I find it hard to read other people's, or even my own code (parsing nested if conditionals is no fun when you're debugging under duress), and CSP is really just.... Not the best concurrency paradigm.
- otabdeveloper4 7y agoThere's no such thing as "C/C++".
- dnautics 7y agoSorry c/c++ family. Explicit is better than implicit. Pardon me. C was my second real language after Pascal and c++ came immediately after that in a 6 month timespan, so for my underperforming and scelerotic brain (aside from an ld_preload shim I wrote two years ago haven't touched them since the aughts) they are "together" in my brain. Curly braces and all that.
- solarkraft 7y agoI fully disagree. I find Go very nice to read.