[wrp]

Ruby has been referred to as Smalltalk meets Perl, and the problem of dealing with other people's code is one of the main things that kept me in the past from using Perl on text processing projects. The problem of collaborating in Perl was lessened a lot by adhering to Damian Conway's Perl Best Practices. Is there anything similar for Ruby?

[burlesona]

Rubocop and you're done. It's the first thing I'd add to any team project just because life's too short for an inconsistent codebase.

[jherdman]

This. Rubocop is first class. I'm just flat out done bikeshedding in code. If I'm writing JS, it's an ESLint + Prettier combo — or whatever your taste is, I just don't care. Let's write code and let the machine deal with making sure it isn't too ugly.

[ashtonkem]

Ruby’s heavier use of key words rather than symbols saves it from the worst of Perl.

Yes, there’s still some symbols, but nowhere near as many.

[wrp]

The "line noise" aspect of Perl never bothered me, because I'm already a heavy user of regexes. The cause of my misery was Perl's "There Is More Than One Way To Do It."

[cutler]

TIMTOWTDI is what I loved about Perl and the reason I found the transition to Ruby so enjoyable.

[allis10]

For what it's worth, non-alphanumeric Ruby is Turing-complete: https://ideone.com/55WtMM

[qiqitori]

Explanation: https://threeifbywhiskey.github.io/2014/03/05/non-alphanumer...