>>34
The more verbose, the higher the chance for a programmer error.
In a C solution, you'd iterate the array by either using a counter or ... incrementing the array's pointer or some magic. If you mess one of them up, it's over -- you've got a bug.
The Ruby solution, on the other hand, only has to worry about the actual operation on the data, nothing else.