Programming languages are a deeply personal topic (not sure these days, some say it doesn't matter any more, others say it matters more than ever).
Every 6 months, no kidding, I look at Go longingly. Native single binary deployment, nice quick compilation, non-fugly build system and tooling, okay-ish syntax[0], excellent ecosystem, pretty good performance OOTB, much to like!
And then I go writing it, nope out in first 30 minutes and 6 months later the cycle repeats. For some reasons I just cannot stand those anemic enums[1], even before I get to error handling (yeah, I know).
I like that Go.is out there, and people enjoy it, I really want to enjoy it, but turns out my brain doesn't really want to like it. Oh well.
Hope to see Go around for another 17 years, just so I keep learning from a great attentive team behind it.
[0]: I never quite gelled with Haskell/Ruby like statement-ish syntax, nor Python's significant whitespace
[1]: no encapsulated values, no pattern matching, not to mention the fact that they're just bloody integers internally
Go is that one language I enjoy using at work, but would never-ever touch recreationally. Its aggressively mediocre, which is great because you can get going and contribute to any codebase with relative ease, but as a hobby language its shortcomings are glaring.
I always wanted to like Go but until they added Go Modules, I never got really into it. Since then I write virtually everything I do in it and I'm still so happy that I have found something that really fits my vibe in so many ways.
Oh really? I still remember how suspicious I was when Google released it. Turns out, it wasn't that bad after all. (Even though there exist better languages ;-)
e3bc54b2 | 3 hours ago
Programming languages are a deeply personal topic (not sure these days, some say it doesn't matter any more, others say it matters more than ever).
Every 6 months, no kidding, I look at Go longingly. Native single binary deployment, nice quick compilation, non-fugly build system and tooling, okay-ish syntax[0], excellent ecosystem, pretty good performance OOTB, much to like!
And then I go writing it, nope out in first 30 minutes and 6 months later the cycle repeats. For some reasons I just cannot stand those anemic enums[1], even before I get to error handling (yeah, I know).
I like that Go.is out there, and people enjoy it, I really want to enjoy it, but turns out my brain doesn't really want to like it. Oh well.
Hope to see Go around for another 17 years, just so I keep learning from a great attentive team behind it.
[0]: I never quite gelled with Haskell/Ruby like statement-ish syntax, nor Python's significant whitespace
[1]: no encapsulated values, no pattern matching, not to mention the fact that they're just bloody integers internally
nemin | an hour ago
Go is that one language I enjoy using at work, but would never-ever touch recreationally. Its aggressively mediocre, which is great because you can get going and contribute to any codebase with relative ease, but as a hobby language its shortcomings are glaring.
mxey | an hour ago
I always wanted to like Go but until they added Go Modules, I never got really into it. Since then I write virtually everything I do in it and I'm still so happy that I have found something that really fits my vibe in so many ways.
xyproto | 3 hours ago
Quick compilation speeds, easy deployment and a useful feature set for 17 years. Congrats, Go.
hwj | 5 hours ago
Oh really? I still remember how suspicious I was when Google released it. Turns out, it wasn't that bad after all. (Even though there exist better languages ;-)