The most obvious advantage here is that the code at the left is much more concise. This is good because then more code will fit in the same screen.
Not sure this is what Go needs though.
Not sure this is what Go needs though.
Yep, a generics prototype would be better spent time.
We generally don't code on 80x25 character terminals anymore, super high res monitors are cheap, vertical lines in code aren't a scarce commodity.
Personally I tend to like a fair amount of vertical whitespace (either in pure whitespace form or comments) in my code to split things up logically, even within the same function and when the newlines aren't required, eg:
x = 10
y = 20
z = 0
speed = 80
If you think you are getting conciseness by decreasing readability then you probably have a balancing issue, but if you can get more concise code without decreasing readability then that's good news.
100 chars/line better than 200. 60 better than 100. I don't know where it bottoms out.
That's how it's a good thing (not sure if you were being serious).
On the other hand many young developers these days seem to think, that scrolling is good and insert lots of blank lines everywhere.