The Inevitable End of Ruby Programming

None of the none of Ruby's current solutions are on par with those. It's {ts:231} far too conducive to what programmers call foot guns. I never heard that. Features that make it all too easy to {ts:238} shoot yourself in the foot. Huh, that's true. Critically, JavaScript was bad that way, too. Anyway, critically, {ts:245} Ruby's performance profile consistently ranks near the bottom read slows among the major languages. You may remember {ts:252} Twitter infamous fail whale. The error screen with a whale lifted by birds that appeared whenever the service went down. {ts:260} You could say Ruby was largely to blame. … {ts:362} which I'm not sorry to see. Ruby now finds itself awkwardly in middle ground. Uh you may wonder why people are still {ts:369} using Ruby25. It surv it survives because of its parasitic relationship with Ruby on Rails the web framework {ts:377} that enabled Ruby's widespread adoption and it continues to anchor its relevance.