Yukihiro Matsumoto: “Ruby is designed for humans, not machines”
There&#x27;s a lot of comments of the form &quot;I tried getting into Ruby and it never clicked&quot; that I want to respond to.<p>I think that if you&#x27;re just writing a script to solve a math problem or automate a task, there isn&#x27;t really a strong argument as to whether you should use Ruby, Python, bash any other high level language. You should probably use whatever you&#x27;re most comfortable with.<p>But if you&#x27;re making an application with a database, RoR is an extremely powerful tool. And this isn&#x27;t just a case of Ruby having the best library (in the same way that Python has the best scientific computing library). It&#x27;s a case of the library functionality and the language playing together really well.<p>Ruby statements look more like natural language statements than those in other languages. This is a really helpful design choice when you&#x27;re building a crud application. In that context, you&#x27;re not thinking about X, Y, -Log(X + Y) or whatever.<p>You&#x27;re thinking about a <i>new customer</i>, or whether some old customer is a <i>member?</i> of some mailing list, etc<p>In a weird way, it&#x27;s similar to how Haskell users love the fact that statements in Haskell are mathematical truths. In the case of logic programming this is a handy feature to have. In the case of writing the business logic of a CRUD app, it&#x27;s handy if your statements look like natural language statements about the underlying real world objects whose representation you are reasoning about.