3 ms·

Hideous? Why? Are the "do ... end" blocks really that bad? It's surprising for me to hear this, because IMO, Ruby is among the most aesthetically pleasing prog

• mvdtnz 3y ago
  In this case, hideous because of the overloading of =. But in general it's just an ugly inconsistent mess of a language. It can't decide if it's supposed to be expressive and read like English (begin, end, rescue, unless, etc) or needlessly terse by omitting random vowels (elsif, strftime, uniq). And then there's the utter mess that large codebases get into with metaprogramming.
  • trealira 3y ago
    Those are fair critiques. Thanks for the response.
• trevor-e 3y ago
  For my brain it's an incredible amount of noise to parse through compared to {}. Especially in addition to the amount of things you have to keep in your head since there is no typing to rely on.
  • vidarh 3y ago
    To me the incessant {} adds an incredible amount of noise. And I don't think I ever go around worry about types. If the typing isn't obvious, then that's a big warning sign to me about how the code is structured.