This is just a sad Stokholm defence - against languages that threatens your sacred cow - which is understandable since the Java code example got pwned. So rath

This is just a sad Stokholm defence - against languages that threatens your sacred cow - which is understandable since the Java code example got pwned. So rather than defending the code example on merit, you dive into pedantic nit-picking territory. I used to be defensive about my choice language as well, till I matured and realized holding onto sacred cows just hurts your ability to learn from others doing it better and being more productive; and just clouds your ability to choose the right tool for the job. More code = more code, to read, to decipher, that hides intent, that adds complexity, that can have bugs and can go wrong. Code-size is codes worst enemy. I don't even know Ruby, but it's implementation is vastly more readable and would look a lot closer to what the perfect DSL would look like for this task, than the Java example.