<story><title>Ruby&apos;s switch statement is flexible</title><url>https://www.akshaykhot.com/ruby-switch-statement/</url></story><parent_chain><item><author>MrVitaliy</author><text>Ruby is going through some kind of renascence age, I&amp;#x27;m seeing allot of Ruby articles lately.</text></item></parent_chain><comment><author>SkyPuncher</author><text>I feel like people got hung up on computational performance for a while. 5 to 10 years ago, a bunch of big startups hit the scale where they needed to intentionally work around Ruby&amp;#x27;s limitations. People seemed fixate on those performance issues while overlooking the business context - that hitting that scale means you are wildly successful and solving problems most startups never have the chance to solve.&lt;p&gt;It seems there&amp;#x27;s a swing back towards people considering raw productivity. Especially, at early stage or pre-product market fit.&lt;p&gt;Given that Rails is highly correlated with Ruby usage, it&amp;#x27;s simply hard to beat how much productivity and breadth that Rails gives you. Especially, with how much &amp;quot;grunt&amp;quot; work is easily handled by it.&lt;p&gt;I love trying new frameworks on side projects, but I always find myself coming back to Rails. There is inevitably some nuanced situation that the framework doesn&amp;#x27;t handle that would be ridiculously easy in Rails.</text></comment>
<story><title>Ruby&apos;s switch statement is flexible</title><url>https://www.akshaykhot.com/ruby-switch-statement/</url></story><parent_chain><item><author>MrVitaliy</author><text>Ruby is going through some kind of renascence age, I&amp;#x27;m seeing allot of Ruby articles lately.</text></item></parent_chain><comment><author>imacomputertoo</author><text>I love Ruby so much. Its syntax and flexibility are such a joy to work with. I hope it does have a resurgence in popularity. I&amp;#x27;ve been using it my whole career, and fearing the day I have to switch to something new.</text></comment>