Thanks for the response.
Lasse Ebert

map-reduce looks fine here, yes, unless you have dozillions of items, all having short (to be precise: shorter, than 23 bytes) messages.

In that case map to message (when message fits RValue size) will increase amount of Ruby Heaps, which are not GC’ed (read: memory is never returned back to OS.)

My point is: one should not abuse languages by using wrong paradigms, even if the latter is fancy, fashioned and has all the hype around. Ruby is ruby, and mutating a string here is the right approach. Even if it sounds COBOL-like solution.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.