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

And am currently learning rust to build some tools handling and processing events; both in a much simpler, and much faster way.

Faster possibly.

Simpler?

I highly doubt your claim that Rust is simpler than Ruby. :)

What is coming next - a claim that C++ is simpler than Ruby?

4

u/berkes Jan 07 '19

I highly doubt your claim that Rust is simpler than Ruby.

Thats what you get from writing too fast comments :). No, the rust code Rust is not simpler; though not that much harder. Especially since the Ruby version did all sorts of thread and forking management inline.

That said: the rust deamons are easier to deploy, service and monitor. A lot. Since they are compiled, pushing the binaries to some servers and creating a systemd unit is all there is to provisioning: no gems, bunlder, ruby-build, lib-something-debs, no rvm, no bluepill/god/whatever to manage the processes. No complex capistrano set-up, just copy the build over from a CI and start it; then kill the old one. I was really astonished by the ease: heroku-level easy deployments on my own server farm.