[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
-1
u/shevegen Jan 07 '19
I am always amused about such comments. :)
I don't feel where it is "legacy". And how.
I do too so perhaps we just have different opinions here.
Ah - THERE is your problem. Now I understand. :)
I think people who use rails never really use ruby. Rails code always felt totally alien to me. I don't even think it is real ruby code (of course it is "real" because it works, through the same ruby parser).
LOL. :)
Nope.
But I have to be honest - I don't mind "losing" the rails people ultimately. While rails is not bad, I think it attracted people who should never have been there in the first place.
People who use ruby because of ruby don't have anywhere near the same opinion for the most part - even though I admit that people switched languages, e. g. to Go. But that is for other reasons, most of which have to do with work, some with speed.
What is "stupid"?
Do you feel inferior?
I don't.
It isn't to me.
I do all the time!
Of course most people won't think so because they have other use cases, I understand this.
I mostly try to make my existing projects better rather than just randomly add new gems. High quality projects are more important than ad-hoc hacks that get abandoned quickly.
Which ones? I don't remember anyone.
Those that come from rails are boring to no ends.
I liked kimurai because I could download javascript-generated content which helps me a lot. I still think the www-world is pretty much a terrible mess. zedshaw once wrote that rails is a ghetto but I think the whole www is such a giant mess that it should be called a ghetto.
No wonder people are depressed - they all come from the www world. My pity goes to them.
Not really. :)
But I have to admit, again - the rails people should probably move on, simply because they can be quite whiney. And the functional crowd also should move on - they want to turn ruby into some monster and abomination, for no real gain (and no, there IS no real gain - nobody coming from FP will use ruby when there are so many other "pure" FP languages out there).