Flipside, I love Python and hate Ruby. It's easy to use Python idiomatically, and this design deters bad behavior from "clever geniuses". Ruby code I've had to maintain is full of mixins, dynamic dispatch, and magical behavior from a distance. This is why I love Rust so much despite the fact that it feels like Ruby at a superficial level - it doesn't want you to be clever.
But I feel the same way you do about PHP.
> "it's existence is the main brake slowing [...] down."
Maybe Ruby could focus on winning over the PHP community instead of trying for the data science community.
I had to do some hacking on discourse (the OSS forum package), and the amount of magic and difficult-to-follow logic is super high.
Basically, ruby is the new perl, as far as I can tell.
What's new in ruby? it's there since 1995, and the connection to perl was an explicit influence in its design.
In general, this whole thread completely misses the point Python makes. Do not invite “clever” language (ab)use. Do the straightforward thing.
Only by its BDFL. Most languages consider lambdas to be first class so why not let the user decide?
Part of what has also kept Ruby lagging is also cultural. It’s not a language that was ever adopted by engineers but rather artists, and it took a while for these artist types to realize performance actually matters.
Python, on the other hand, always had an avid base of CS oriented folk that helped drive the language forward technically. Ruby instead only had Rails, which was a productivity marvel rather than a technical one.
… are none of the engineers that work at GitHub (Microsoft) CS oriented folks?
> Ruby instead only had Rails, which was a productivity marvel rather than a technical one.
… are productivity marvels and technical marvels mutually exclusive?
And sure, some of the engineers at Github/Shopify/etc are super qualified but from my personal experience in the Ruby ecosystem (5+ years and counting) there are WAY more autodidact freelancers who can throw up new websites in minutes but still struggle with computing the algorithmic complexity of linked lists than there are CS graduates who have a solid grounding in data structures and algorithms. In such an environment, it is not surprising that many of the available libraries are very business-oriented but not very optimized.
Ruby and it’s ecosystem make things look easy. So easy that anybody can create software.
The elitists fail to see that creating such an ecosystem is where true skills and thinking required. Funny part is most of them ARE sheep, and make so many basic and architectural mistakes. They simply like to feel superior to others.
It is true IME that usability and compatibility, not performance, are Matz’s first concern.
Can't tell you the amount of times I've been able to just put pseudocode down in Ruby and have it work somehow, the language is beautiful
I'll address the points you made since I love talking about Ruby lol, hope you don't mind!
I'm not sure what you mean with the 3.times {} point. I personally prefer the 3.times do ... end syntax, because it's basically English, it makes it very easy to comprehend what's happening as a beginner. You're doing a thing 3 times, it might as well be pseudocode. IMO it's much more elegant than the whole for (i = 0; i < 3; i++) syntax that's more common in other languages.
The optional return thing I'd agree with, it can lead to some confusing situations. Even after years of Rubying, I sometimes get caught by an unexpected return, especially if I'm working in other langs for a bit. Though if you just disable Rubocop's warnings, you can put a return in no problems! I even encourage beginners to explicitly put in returns, so that the methods they write do what they intend them to do. Didn't intend to return that specific thing there? Now it's clear!
What specifically about strings and symbols? The only caveat that I can think of is that symbols are immutable whereas strings are not , but I don't know how often beginners come across situations where they're confronted with symbols outside of a Hash anyway.
The hash conventions are simply a matter of legacy code. I forget when the rocket (=>) syntax was 'replaced', for lack of a better word, but that's just because before a certain version of ruby you couldn't do the foo: :bar syntax. For legacy purposes, the rocket one remains, but in my experience most people writing modern ruby stick with the foo: :bar convention.
I'd also agree with the optional parenthesis bit, though again for beginners I just tell them to always put parens since it makes it easier to reason about methods.
After all, people did flock to Python for integration with scientific, math and machine learning libraries, not to Ruby.
There are some musings, for example, here: https://twitter.com/zverok/status/1365014133180141578?s=20
I don't hate python but it's existence is the main brake slowing ruby down.
I enjoy programming in Ruby. As the years roll by and I get more grey hairs the enjoyment I get from other languages descends to just toiling away and wasting one's life.
Thank fuck for Ruby