Re:Half a million lines of Go
by unscaled on Sunday May 16, 2021 @10:21PM
(#27179469)
I think you can summarize the go flavour of "readability" as:
Fewer constructs for the price of higher Signal-to-Noise ratio.
Go eschews almost any kind of syntactic sugar that might be unfamiliar to you.
The endemic "if err != return err" issue is also highly indicative of this choice.
I really find that quite hard to stomach. For small apps, this can be acceptable, but for any Go app that gets large enough, this trade-off becomes untenable. You have to scan through too much visual noise to get a clear understanding what the code is doing.
Re:Half a million lines of Go
by dcow on Monday May 17, 2021 @12:20AM
(#27180014)
Go is a language for writing microservices that handle http requests and/or client-side networking "clients" to an api served by said microservices. My guess is the tradeoff is okay in 95% of those scenarios.
Fewer constructs for the price of higher Signal-to-Noise ratio.
Go eschews almost any kind of syntactic sugar that might be unfamiliar to you.
The endemic "if err != return err" issue is also highly indicative of this choice.
I really find that quite hard to stomach. For small apps, this can be acceptable, but for any Go app that gets large enough, this trade-off becomes untenable. You have to scan through too much visual noise to get a clear understanding what the code is doing.