Re:Ten Years of “Go: The Good, the Bad, and the Meh
by omegabravo on Tuesday July 18, 2023 @02:56PM
(#36777542)
Being able to read your code you wrote 2 years ago does wonders for survivability, which is a gross simplification of course.
It's a great language for some problems, horrible for others. The problem is people tend to talk as though everyone works in their domain.
Re:Ten Years of “Go: The Good, the Bad, and the Meh
by monksy on Tuesday July 18, 2023 @05:03PM
(#36779072)
> Being able to read your code you wrote 2 years ago
It won't stop you from asking wtf did someone write this and then doing a git blame and seeing your name.
Re:Ten Years of “Go: The Good, the Bad, and the Meh
by kaba0 on Tuesday July 18, 2023 @06:42PM
(#36780020)
If “each individual line is easy” would work, we would be reading-writing in assembly. I don’t accept the premise that Go would be any better in this region, if anything, it is worse by cluttering up the happy path by error “handling” noise, and much harder than they should be opewtions.
I'm not sure that this successpoint is really that valuable. It sounds more valuable for those who want butts in seats than it does for long term satisfaction and survivability of your code base.