<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Rails - Tag - vo.rs</title><link>https://vo.rs/tags/rails/</link><description>Rails - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Thu, 22 Dec 2022 17:15:14 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/rails/" rel="self" type="application/rss+xml"/><item><title>Ruby the good, bad and ugly</title><link>https://vo.rs/story/ruby-the-good-bad-and-ugly/</link><description>&lt;p&gt;The first time Ruby genuinely surprised me, I was reading someone else&amp;rsquo;s code and understood it on the first pass without running it. That sounds trivial until you&amp;rsquo;ve spent a week deciphering a clever one-liner in another language. Ruby reads like a slightly terse version of what you&amp;rsquo;d say out loud — &lt;code&gt;3.times { puts &amp;quot;hi&amp;quot; }&lt;/code&gt;, &lt;code&gt;[1, 2, 3].select(&amp;amp;:even?)&lt;/code&gt; — and that legibility is not an accident. Yukihiro &amp;ldquo;Matz&amp;rdquo; Matsumoto started designing the language in 1993 and released it publicly in 1995 with an explicit, almost stubborn goal: optimise for the happiness of the programmer, not the convenience of the compiler. Nearly every strength and every wart in Ruby traces back to that one decision.&lt;/p&gt;</description><pubDate>Thu, 22 Dec 2022 17:15:14 +0000</pubDate></item></channel></rss>