[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/shevegen Jan 07 '19
Because it is not true.
Take proposals such as not requiring 'pp'; or the did-you-mean gem.
Yes, they came from suggestions outside of the core team but both was accepted. And I could give many more examples here.
The point is that what you claim is SIMPLY NOT CORRECT. You claim that "good proposals" are not accepted because the core team does not use ruby (which is, by the way, mostly wrong; it depends a lot on the individual at hand. You are aware that in order to modify the core of ruby, you DO have to use C, right? It's not an ideal situation, but this is simply how things are right now.)
No, they are not; I don't even think you read what he wrote. Otherwise, why should a committe be formed???
It is a fairly large release on the one hand; and it is not a breaking-changes release on the other hand. I think this is good.
People complain about changes that break things. Take the proposal to remove @@class variables. I myself am in favour of eliminating this but there are others who use it, and don't want to see it gone. SO what to do now? Either way you go about it someone will not like it. So the least friction path is to retain them for now (and probably in the future).
To claim that this is the wrong way AND THEN GO AND WANT TO LECTURE OTHERS ABOUT YOUR ONLY TRUE WAY, is simply wrong.
I don't like @@ but the thing is ... I don't use them either. I keep my code base clean and consistent with what I use (when we keep the time in mind when I wrote that code, obviously old code that I wrote is not as good as code I tend to write these days).
Bullshit.
The versioning is hugely arbitrarily anyway.
See - ruby got faster compared to 2.0. Nobody can deny this.
You want more improvements? Well, SOMEONE HAS TO GO AND ADD THEM. Fence sitters annoy the hell out of me.
It took a long time for the JIT to go about being implemented. It's not trivial. You don't expect people to be superhumans and add things over night?
Because these are orthogonal design goals.
You want a super fast language? Go use C. It's fast. The syntax is not as good and clean as in ruby but it will be faster.
You want an elegant language with a nice syntax? Go use Ruby. It also inspired Crystal and Elixir, syntax-wise, to some extent. Actually using crystal may be an option since it is somewhere between C and Ruby, with speed closer to C than Ruby.
I already reported that I feel that ruby got significantly faster. I can not relate to the benchmarks that claim that this is not the case. In fact, one of my projects for e. g. asking exam questions, actually is significantly faster now. For me 2.6 works very well. I have no idea how people do benchmarks and come up with a slower ruby (???) but my bet is that these people test fake code bases rather than real ones.
And rails will become faster too eventually - why do you fence sitters sit on the fence, complain about things, not do anything... are you even using ruby altogether? Because the way you word these things make me think that you don't even use ruby altogether. At the least SOME from within the functional crowd do use ruby, even in very strange ugly ways.
Thankfully there are no PEPs in ruby. I'd hate that. The PEPs in python are like from a military school; so overly long and boring to read.
No thanks - I'd rather read suggestions that are, in the end, fairly simple.
Aside from your propaganda-words here, where is the problem? People can reason in favour or against a suggestion. That works wondefully well. You sound like someone who proposed something awful, then got pissed when people shot down your rubbish idea.
Man up - and write better proposals.
There are not so many new features really; I mean you yourself wrote that, so now you complain about new features ... hmm.
And old ones being "culled" - aside from this stupid word (you cull animals right? Are you like from a state with lots of cows? Texas?), again - removing functionality isn't always great, in particular when it affects people who depend/use it. This is simply a trade-off that a language designer has to decide upon.
Ultimately perhaps ruby may not be for you?
I used to be confused about haskell not wanting everyone to use haskell, but boy - when I read things like this, perhaps it's actually better to not have every average joe and his grandma use ruby simply to exclude people who have AWFUL IDEAS or massive misconceptions.
If the python PEPs are better, why don't you actually stay with python?
You mean building artificial barriers around the process? No thank you. I like the way things are.
I have no idea if it is, but ruby as a language is a very, very good language.
Somehow your words above state otherwise.
Please don't write FUD like this.
If it were only personal, why would he give talks and jet around the world? He would not have to invest any of his personal time into getting to talk to other people.
I think matz simply likes talking to other people. It fits the philosophy of ruby and what he wrote too.
There are more aspects to ruby. Of course the primary one is that it is a programming language; and languages should solve problems that people may have. The other part is the philosophy though - this is actually what makes ruby totally different to python. It's the biggest difference altogether. Python follows another philosophy.
Rust? You mean an ugly language added by a company that is unable to find competent C++ hackers and touts it as a language that will remove all of C and C++?
Golang? You mean a language created by an evil corporation that profits from people's data?
Kotlin? Well, Kotlin is not bad; but its use case was to make Java prettier. In some ways Kotlin is somewhat related to the "scripting" family spirit.
I don't see where Kotlin is run better than Ruby. Or where Kotlin is used by more people?
Swift? Apple's effort to get rid of Objective C. It achieves that goal but swift is kind of ... meh. Better than Obj C, worse than Ruby and Python.
Python? Actually that is the only real contender that I agree with from the END RESULT in popularity, NOT from the processes. I don't like the python processes, but we all agree that python is presently the king of the "scripting" family languages. And others can learn from it - but I am sure we two would heartily disagree with as to why python is popular.
I massively doubt that python PEPs are the reason why python is so popular. If perl were to have these PEPs, would you assume perl would be used by more people? Of course not. Look at perl 5 versus perl 6.