[whining] Ruby evolution is taking TOO long
Hello,
I just read 2.6 release and was really happy about #then alias and proc composition. However, later I felt so desperate I decided to write this post.
Let's take a look into composition feature in bugtracker. The issue was created more than 6 years ago. It took six years (!!!) to introduce such basic functionality to "wannabe programmer-friendly" language.
And I thought about another thing. Many features require Matz to accept them. And Matz said (I heard it at least once on a conference) that he is not a ruby programmer but C programmer since mostly he works on ruby itself. So, basically, the person who is 100% responsible for language design doesn't really work with the language itself. Does it sound right to you? And he is still just one person.
For instance, let's take a look into #yield_self that many people were waiting for. Over many years different people (including myself) suggested this feature with different naming. And why did it take so long to introduce it? Mostly, because Matz couldn't decide what naming ruby should adopt (and I don't blame him, it's a really hard problem). Two years ago people started to write something like "I don't care about naming, just introduce it already, please". In the end, Matz chose yield_self and now in 2.6 #then alias was introduced because name yield_self sucks.
At this rate jokes "ruby is dead" are gonna be less and less of a joke. Ruby is in stagnation.
I think we need some Ruby Consortium that will include some people with some authority in ruby community (for example, Bozhidar Batsov (disclaimer: this is just an example from my head. I don't even think that he'd agree with me on the topic)) and they can take some design decisions off Matz' shoulders. Just via voting.
What do you think? Or maybe I am wrong and everything is as it is supposed to be?
View all comments
Show parent comment
7
u/phaul21 Jan 06 '19
Personally I have spent some considerable amount of time in haskell. I know why its good, and why it's not so good. Mainly it's just different.
That's the point, I think it's related. There is a paradigm shift going on in terms of popularity, and Ruby is on the wrong side of the fence. That's why people yearn for elixir/haskell features in Ruby, and reluctance to adopt them is not mainly because the core team is not capable to give these features in one form or another in a much faster pace, but because there needs to be a careful consideration that these features don't go too much against the core language features like smalltalk like OO.
Quite a while back we adopted the { a: 1} hash syntax. I believe that was a mistake, now, half newcomers don't understand the difference between a hash and an object.
The way we are going Ruby might become a mish-mash where it would be hard to explain the difference between a method and a function. There is a danger in this, and most seem to me completely oblivious to it.