Is it bad that the first thought that came to mind upon reading the example code on the page is "Wow, this is ugly"?
...And I don't mean the "if err" sprinkling that has a whole subthread, I mean the actual layout of the code. It's not hard to understand just.. ugly. Aesthetically. And it's hard for me to put my finger on why.. maybe it's the symbols everywhere.
I was about ready to make a remark about how I hope that's not idiomatic go code, but no, this is from the official site.
I've never wanted to like a language that makes me not want to like it as much as Go, and that's the god's honest truth.
> It's not hard to understand just.. ugly.
To me, code that's easy to understand is beautiful. If you've got different ideals, then probably go ain't the language for you.
Or use it for a while, and you may find your standards if beauty shift.
Re:Introducing HTTP Tracing
by zenlikethat on Tuesday October 04, 2016 @11:19PM
(#12641321)
Give it a chance. I feel the opposite in many cases today because of two reasons: static typing and gofmt. In Python code I frequently find myself playing "what the hell are these objects" or "what the hell does this overloaded operator do" and in lower level code (esp. C++) it looks like a mangled jaggy mess. Linux kernel code is one of the few exceptions due to the strict style guidelines.
lots of time I see people compromise readability to chase this "beauty" and "elegance". Go makes this practically impossible.
Python is pretty readable but it doesn't look like someone smashed the keyboard while holding down the shift key.
On another note, it's pretty f*cking lame that the only discussion in this post is a tangent about error checking and not even remotely related to the content.