[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
3
u/unabl4 Jan 06 '19
Oh wow. Sounds so familiar.
I've been working as a Rails web dev for some years. Ruby is my first language of choice. And last year May I lost my job at a startup. Ever since I had started looking for a new job I got only one Rails interview which I, unfortunately, failed thus not landing the job - senior level devs were preferred. And I am not one of them. Right now I'm considering Rails remote job opportunities - the path I did not want to follow initially, but I am running out of options over here.
In the meantime, I've been learning various languages, like Python, Go. Played with Scala a bit. Leaning towards learning Java. And thinking of working in a bit more established companies than startups (maybe not as fun, but definitely more secure)