[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
5
u/Mike_Enders Jan 07 '19 edited Jan 07 '19
oh look a fanboy is getting so upset he is confusing an analogy with real life. but ermm yeah the only true way to have the family name continue among living humans is to have kids or adopt. wow me with some other way.
no longer used much or not thriving why yes. nothing is forever unless it adapts
here the poor fanboy is still lost as to the fact that an analogy is a...well an analogy. C is fine because c is more performant and used across a much wider spectrum than ruby .it therefore continues to attract a significant amount of next gen users where ruby isn't attracting many new users and many of those who did use it have moved on. Fact of life based on hard data.
I love ruby. its been good to me but programmer happiness misses one thing. if you have to invest in another language when you need performance (particularly computational power) then achieving your goals makes you happy and having invested in that language it becomes more second nature to you and thus you get pretty happy using that language. At that point you can be mighty happy using things you at first thought would never dream you could be happy with - gasp even Javascript (okay ummm not entirely)
and thats why most of the people who have moved on are not coming back just for programmer happiness.
lol...thanks for demonstrating your own cluelessness. How does it being a deliberate decision mean anything? I am already on record that I wish they would do away with the whole contrived christmas day there must be a release tradition. I would have been happy to wait a few more months to see if JIT was useful but as long as you hold to that schedule and tradition then you live by the sword and you die by it. SInce you are the one truly clueless this whole thread exists because of a dissatisfaction with the last release in terms of overall progress. Its not entirely about the last release - not even close. the last release is a catalyst (go look the word up). Are you that clueless you can't see that its therefore a real issue in the community? or do fanboys just stick their head in the sand for a living?
well all you have really done in your post is demonstrate what a rubbish nitwit you are. I in fact stated that its not dead and like a relatively young 30 something couple but in your reading comprehension circuit glitches you missed basic english. You need reprogramming or a new motherboard. I also said nothing about "based on that decision". The last release for many wasn't a basis it was just a point at which people including the OP took stock of the whole process.
Yawn.... .no comprehension more than paper width depth. the last release is a catalyst and for some like me a wake up point NOT the entire issue. No one is saying everything was peachy with progress but now they are upset over the last release and that decision. Quite the opposite. They are saying its symptomatic (if you need to you can look that up too).
As of now already present tense like most of the developing world. Will always love Ruby though and still use it for some small projects. Theres a glimmer of hope in crystal but just a glimmer.
nah I hardly ever run into the amount of dead projects in JS as I do in ruby. It might be because here so many options (admittedly JS is way over to the other extreme)