5 ms·
My appreciation for Go has been monotonically increasing for years. The more Go code I write, the more I like the language, the tools, and the standard library
by 37ef_ced3 5y ago
My appreciation for Go has been monotonically increasing for years.
The more Go code I write, the more I like the language, the tools, and the standard library.
Low-friction, high-quality software development.
If only I could use it professionally, instead of C++.
- theshrike79 5y agoGo is the choice of professionals IMO. When you have a team of varying skill levels who need to deliver shit that works on a schedule and still have some kind of performance, you use Go. Even more so if you need to hand off the maintenance to a team of randoms from god knows where and THEY need to be able to keep it running and add new features. It doesn't have the fanciest new EXPRESSIVE operators or anything exciting really. It just does the job, albeit verbosely. You can do fancy shit on your own time.
- int_19h 5y agoI would argue that e.g. decent error handling is not "fancy shit".
- theshrike79 5y agoIt's perfectly decent, it forces you to explicitly handle or ignore every error. It's verbose as all hell, but on the other hand you'll notice immediately if it's missing. Go is not a "fun" language by any means, but that doesn't mean it's not a productive one.
- int_19h 5y agoI don't see how it forces you to ignore? You don't have to be explicit to ignore the returned error code.
- theshrike79 5y agoThat's what the underscore is for, explicit ignore. And it's a huge code smell. You instantly notice it because the if err != nil -template is missing after it =)
- int_19h 5y agoSorry, I didn't word that well. What I meant is that you can ignore the returned value altogether, including the error. https://github.com/golang/go/issues/20803 https://github.com/golang/go/issues/20803 In contrast, e.g. Zig requires you to use _ if you want to ignore.