This is actually one of the things I first liked about Ruby. Then it became one of the main reasons I started disliking Ruby.

It seems the opinionated, directive "there's only one way to do it" approach is winning over the hacking around, "wrapping around your mind" approach. Lisp and Perl have had their times under the sun, now it's all about Python and Go. Perhaps these things are cyclical.

I'm using both Ruby and Go a lot (also Elixir, PHP, Bash and others).

I wouldn't even say that they solve different problems for me, it's more a matter of how I need the problem solved. If I need something that runs on other OSes than my Linux box preferably with as few dependencies as possible, Go. However, I can probably code it faster in Ruby, so if it only needs to run on my machine or if I know Ruby's available where it needs to be run, then I'll probably go with Ruby.

I think, instead of arguing which is better, the argument should be about whether they're useful. And for both Go and Ruby that's an "absolutely!" from me.

I'm just happy that there's still a popular language around that lets me write how I think (or however _I_ think would make the code look the best), so I don't have to suffer through using languages that direct how I have to write every little thing.

Having both options is nice!

It's great if you're the only one who ever has to read or maintain your code.