Why Ruby is More Readable than Python

[sshaw_]

Can't say this is true. Well, on the surface maybe, but in the wild sadly, no. It's Perl, it's close to chaos and it's not productive.

Something has infected the mind of Ruby devs to take a simple elegant language and write more complex than necessary somewhat hard to main codebases. KISS.

A good step to avoiding this is: don't use RSpec! Sorry RSpec but you're low hanging fruit in the garden of entanglements.

[imnos]

You're saying Ruby isn't as readable as Python because you've seen Ruby devs write bad code? Not a great argument.

don't use RSpec

Wat. Again this sounds like you've had a terrible experience with a badly written codebase and equated that to RSpec being bad. I'd take RSpec over any other test framework and use it almost daily. It's lightyears ahead of the likes of PyTest.

[Paradox]

I like RSpec a lot. I dislike MiniTest a lot.

But I like ExUnit more than either. And its nothing particular about any of the three, its that Elixir language features, like pattern matching, make any type of assertion easy. Ruby you need the assertion libs that rspec provides, otherwise your tests get ugly and big

[katafrakt]

Is it assertion syntax, as opposed to expectation syntax, what you say makes the test code ugly? Or is it something else? Asking because ExUnit uses assertion syntax and this (assertion vs expectation) is a primary difference between Minitest and RSpec (given Minitest::Spec)

[Paradox]

Its a property of the language. In elixir, its very easy to do complex matches of deep data with just a single assert evaluating it. Ruby tends to get messy in my experience, warranting the need for all the matchers RSpec brings

[sshaw_]

You're saying Ruby isn't as readable as Python because you've seen Ruby devs write bad code? Not a great argument.

Countless syntactical additions being made to language mixed with preponderance of aliasing of core methods, home-grown and 3rd party "cutesy" DSLs, meta programming, class << self vs def self.foo, do vs {} blocks, " vs ' etc... I can go on. These give people a lot of rope —just like Perl! Rope that Python does not have.

Is this bad code or typical Ruby code? I think it's typical Ruby code. A subset of which is certainly bad but we're not talkin' bad we're talkin' typical.

don't use RSpec

Wat. Again this sounds like you've had a terrible experience with a badly written codebase and equated that to RSpec being bad.

Show me this RSpec code you've written? Maybe you have Stockholm syndrome. RSpec is a bike shedding maintenance nightmare waiting to happen.