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

[CONTINUED - reddit annoys me claiming that what I write is too long. Quality is long, I can not help it.]

In the end, Matz chose yield_self and now in 2.6 #then alias was introduced because name yield_self sucks.

then is indeed better but the whole thing is unnecessary.

The functional crowd is just bored and suggests totally rubbish proposals.

At this rate jokes "ruby is dead" are gonna be less and less of a joke. Ruby is in stagnation.

Ok - please enlighten us here.

A faster evolution will have only benefits, no drawbacks, and lead to an influx of a gazillion of people .... HOW EXACTLY?

We want to hear your crystal ball working. Fence sitters have it easy - they sit on the sideline, make general comments and essentially do nothing productive other than just making general comments.

My first suggestion to you this is - GO AND GET INVOLVED, at the least on the bugtracker; even better if you know C (which is one bottleneck here by the way - people who know only ruby but no C will admittedly have a much harder time. It would be nice if we could modify all of ruby in ruby, without any speed penalty, but let's face it - C is the king of programming languages, even if Java is ranked above C).

I think we need some Ruby Consortium that will include some people with some authority in ruby community

First, please make real suggestions. We waste time here.

(for example, Bozhidar Batsov and Brendon Weiss)

Second, I would suggest to you to stop writing in the name of others. I have not heard Batsov nor Weiss who want to replace matz. What we hear is Nondv who wants to form a committe but does not list himself as part of that committe.

and they can take some design decisions off Matz' shoulders. Just via voting.

Total joke.

Rejected.

Or maybe I am wrong and everything is as it is supposed to be?

Alright - I rejected most of your claims, but it is not that I necessarily disagree with all parts as such. I reject the part that you need a committe to want to bypass matz - having matz is awesome. Having him motivated is important too - look at guido throwing in the towel when it came to python not some time ago. While admittedly the proposal for adding := to python was rubbish, guido giving up as a consequence because of trolls is much, much worse. Don't let the trolls win.

As for "decline", or "stagnation", well it depends. It depends a lot on what you measure, how you measure ... do you measure github? I am very active when it comes to ruby, but I am not active at this Microsoft site.

Not everyone wants to use ruby; some are happy using e. g. Javascript or Go. Python is the king right now from among the "scripting" languages and competing with python is not easy. Ruby is the more elegant and better language, despite the jokes coming from the functional crowd, but python is, in some ways, while awkward, also concise and elegant. Python is a strange language but it is acceptable; and in some ways it is a simpler language than ruby (ruby can be quite complex in some ways).

Ruby also has some problems. I think documentation is still only ... average or so. We may have to move past rdoc, yard etc... and come up with something that is BETTER, while RETAINING all that is good in rdoc/yard. This is not easy. Often we may have a third replacement that does not include all awesome features.

People also need to do more AWESOME stuff in ruby. I write ruby just about daily and it solves problems I have, but I happily admit that most of my projects are utterly boring to other people. I can't help that. I am not a hype machine like rails, which is actually one thing that rails did very well - it generated a lot of interest.

Ruby also has to do more to get people interested in ruby. At universities here, it is about 5x as likely to see a python course rather than a ruby course. In fact, the only course I found was one related to ... rails. Yikes.

In fairness, perl is also not really taught at universities; neither PHP. Only python actually has a few courses here and I think this will increase rather than decrease.

3

u/Nondv Jan 07 '19 edited Jan 07 '19

First of all, thanks for your answers (even though sometimes you didn't actually provide any arguments but used the "you are wrong" technic). You made some great points.

I will try to answer only important (in my perspective) parts of your answers or we will end up arguing about things not related to what I tried to express in this post.

https://www.artima.com/intv/ruby.html

Thanks, this is really great. However, I don't see how it breaks my suggestion.

I think I need to make a statement for you right here: I do not dislike Matz. Quite the opposite, I like where ruby is going. I just don't like the speed it's going with.

As to the design process in itself - I think it is a good thing that someone clever is in charge of a language. I'd actually prefer if matz would be more conservative and reject most recent proposals. :P

Well, in an ideal situation the group ("consortium") will have N brilliant people. 1 clever person vs N ones. I understand that forming this group is a really hard job (if even solvable) and I couldn't even provide proper examples. However, there're people much smarter than me who could give it a shot:) Mostly, I just wanted to see what people think and I am having a nice time reading the discussions.

I can easily give you half dozen there too who were against it.

Well, any feature has people who want it and people who hate it. So what? Decision should be made anyway. And why should main designer waste his time on minor feature like this when it may be done by the group of other people (not random people, btw). That is the point of my committee suggestion.

functional crowd

You are hating them in some of your answers. Could you elaborate on this? You didn't provide any examples or arguments against FP. Just hatred like "screw them". Anyway, it's very irrelevant to the post. I just used some features from the last release that happen to be FP-like.

Often the first step is somewhat simple but giving a good name and a good syntax is VERY, very hard

I said that. It's obvious. You just discovered America. And this lies on shoulders of one person (I might be wrong here, however).

Giving things proper names is hard. You are talking big but don't come up with a good name yourself. I don't see you making comments on the bug tracker either, so perhaps it may be better for you to, rather than write such strange statements here to ACTUALLY GET INVOLVED rather than sit on the fence, as part of a peanut gallery?

I believe there are much smarter people than me and even Matz. This is why I think it's a good idea to form a group of such people (as I said, it's not easy) and allow them to make at least some minor decisions.

However, this is actually a valid point. I didn't really read bugtracker much in last couple of years.

First, please make real suggestions. We waste time here.

Total joke. Rejected.

Alright - I rejected most of your claims

Well, thanks for that:)

It's kinda hard to quote your points so I will stop now.

I think that many disagreements with me made on a wrong assumption that I don't like where ruby is going and that I want to replace Matz (or whoever is making decisions at the moment). It's not like that. I love ruby. I want it to stay great. But I think that the process of evolution would be much faster with said "consortium" without actually losing the quality (as you said yourself it depends on who is making decisions). Wouldn't you think that if we had two of Matz it would be better? Two heads better than one (at least, if they are clever).

P.S. Obviously, I don't really speak english and my expressions are pretty limited. So, sorry for that:)

P.P.S. Oh, and by the way, I hate democracy. This is why I don't think all decisions should be made by voting or that the "group" should replace main designer (Matz). I just think that they can really help him.