imo, Ruby optimizes for flexibility over consistency in a way that is unpleasant and lends itself to unforced errors. The Python standard library has never str

imo, Ruby optimizes for flexibility over consistency in a way that is unpleasant and lends itself to unforced errors. The Python standard library has never straight up failed on me in the way that Ruby has. Ruby had buggy named-argument splatting, i.e. func(*kwargs), until 2.7, and even that was a half-realized implementation. It took something like 5 years to fix: https://bugs.ruby-lang.org/issues/11860 https://bugs.ruby-lang.org/issues/11860 I've had similar experiences with Rails.