Hacker News Reader

The difference here is that when you read the title you think: "wow, scala features allows solving interesting problems in few steps, let's see". And the you realize that it's a cheat. This code is literaly squeezed into those 4 lines, full of less common idioms, and quite obscure.

It should be called "0,5kb scala contest" than "solving x with scala", to avoid misunderstanding.

Maybe it's the case here but in the scala community in general I noted a tendency to emphasize cleverness over clarity and simplicity.

Relevant Stack Overflow question: http://stackoverflow.com/questions/7084212/is-scala-idiomati...

This piece of code doesn't "solve" the problem, it's a crude bruteforce implementation. The problem is hard for a reason.

Another way this code could be useful would be to showcase good readability practices, but it doesn't.