Using Go as an example, if I were to write a "Why Go" article, it might look something like this:

1) Simple, one way to do everything. for loops, code formatting, and project setup.

2) Good concurrency (go routines)

3) No exceptions, readable code and error handling.

This article is titled "Why Hy." It should sell me on the language with a philosophy supported by examples, not instruct me on how to write a floating point number (unless the language has a interesting take on writing floating point numbers!)