As someone who really wants ruby to succeed, they were setting themselves up for failure if they knew there was a narrative of 3x faster out there when they kne

As someone who really wants ruby to succeed, they were setting themselves up for failure if they knew there was a narrative of 3x faster out there when they knew that wasn't even close to what people would experience. I think the reality of ruby is that it's a language for people who care more about the feel of the language than its performance characteristics. This may sound like I'm ragging on it but I think there are many cases where optimizing for developer comfort is truly in the best interest of an early to mid stage startup. But don't try to make it into something that it's not like you are competing with rust or something. Ruby simply is not a performance oriented language. That being said it's performant enough for a vast majority of all and medium scale use cases.