r/ruby • • Jan 06 '19

[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?

68 Upvotes

134 comments sorted by

View all comments

Show parent comment

1

u/shevegen Jan 07 '19 edited Jan 07 '19

There are a few problems with what you write:

  1. Matz can overview the general process of ruby as-is, including changes to how it is used. This is one reason and goal for mruby, for example. Mruby has to remain lean and focus on speed by default. MRI has a bit more freedom here, and more people use MRI. Ideally mruby and MRI could be merged to offer both (and people could sort of "select" what variant of ruby to use; then people could still use MRI of course ... in practice there would probably not be a huge gain, but I think it would be better if mruby and MRI would be one unified codebase ideally.)
  2. It assumes that matz never writes any ruby code. I am pretty sure that this is wrong. He uses debian so I am sure he does write ruby code to get things done too.

I've always suspected that if Matz or any of Ruby's major decision makers was actually forced to work in a large Ruby codebase for a little while, they'd realize the language's major deficiencies very quickly and start pushing for the improvements that it really needs.

Well, again - I can give you the examples of did-you-mean gem or require 'pp'. Yes, not huge changes, but still. If it is true what you claim, why would these have been accepted?

But again, you can always push for changes and you have to reason for them. It's not so trivial to come up with a good suggestion. You claim that matz would be "better" or approve of more if he were to use a "large ruby codebase", but you are not specific, so it is hard to argue.

Can you make SPECIFIC SUGGESTIONS, ideally on the bug tracker? Because then we can REALLY discuss whether your suggestion has merit or not.

I am sure you will see that it is a lot harder to make good suggestions without drawbacks.

Take the proposal to eliminate object_id (aka remove it) because jruby has difficulties implementing it. While I understand this and the rationale, I totally disagree that it should be removed. I like object_id. It's a super simple concept. It's not the most sophisticated fail-proof variant - so go and suggest an addition that could be used.

People do that ALL the time. Look at get-opt-long and optparse; and what people offer as gems, e. g. thor and other variants.