I like Go because it's practical. I can hammer out the solution to a difficult problem very quickly and that quick solution is reasonably scalable from a software engineering perspective[0]. Go makes it easy to write the first iteration, but its real strength comes from making it easy to write the subsequent n iterations.
That's "elegance" of some sort, but it's elegance in engineering, not in programming, which is an important difference.
You might say it's "elegantly practical"
[0] By "scalable" I don't necessarily mean performance, but the costs of scaling developer manpower on large projects - ie, a "quick-and-dirty" solution in some languages may require expensive refactoring down the line, or cause you to design bad interfaces in your functions, etc.
"I came to Go expecting the elegance of a ballerina, and was surprised to discover the grace of an experienced bar-room brawler."