In early 2006 I had just started my career in IBM. I was the “Ruby Guy”[1] (or alternatively, the “Rails Guy”). During a meeting with a few high-profile engineers, I presented what Ruby brought to the table. An IBM Distinguished Engineer[2] stopped me in my tracks and said, “It sounds slow”. I love Ruby as much as a programmer can possibly love a programming language, but that engineer’s conjectur