Programming

This mirrors my feelings about Ruby. Especially the lack of type hints. It's a huge problem when trying to work on large Ruby codebases, e.g. Gitlab or Asciidoctor. Easily doubles the time it takes to get anything done. Sometimes I've tried to make a change to Gitlab but had to give up entirely simply because it's impossible to follow the control flow.

That's very rarely a problem with statically typed languages. (It can happen with excessive use of interfaces that are resolved at runtime but it's much less common.)

So aside from Rails I can't really see any reason to use it over even Python, let alone actually good languages like Rust, Go, Typescript, etc.

it's hilariously depressing how most people hate on Ruby because of the shit Rails does.

also, Sheon Han(the author), is a corpo-shilling hack that writes predominantly fluff pieces for his silicon valley friends and neighbors.

don't believe what he writes because he only gets paid when his opinions garner traffic.

want to know why Ruby still has a following? same reason why Java is still holding on. Same reason why COBOL and FORTRAN is still going. because it works and people still use it.

Maybe if I could read the article I'd have something to say about that. I guess we'll never know, and that's probably for the best.

Paywalled clickbaity trash of an article.

The article starts with a lie, imprinting for computer users and the importance for UX is discussed for at least 20 years, see: Baby Duck Syndrome(wikipedia).

One can only think of something like this as "their own little theory", if they are uninformed in both programming and psychology which, after reading this stain of an article, is not far fetched. The correct psychological effect to point out here would be Dunning Kruger (wikipedia).

Hmm, I don't have too large of a sample size, but I don't feel like Ruby programs are buggier than Python programs, on average. Not being the language for programming beginners and data scientists, probably aides that impression, though...

Ruby was the most approachable language I found and sheparded me from my limits of bash scripting and Windows batch file scripting into the next level.

The author derides Ruby's easy readability and syntax because it has issues scaling to large enterprise applications. I don't disagree there is a performance ceiling, but how many hundreds of thousands of Ruby projects never rose to that level of need? The author is also forgetting that Ruby had Rubygems for easy modular functional additions years before Python eventually got pip.

I don't write in Ruby anymore, and Python has evolved to be much more approachable than it was when Ruby was in its prime, however if someone came to me today saying they wanted the easier programming language to learn that could build full applications on Linux, OSX, Windows, and the web, I'd still point them to Ruby with the caveat that it would have limits and they would be better served by Python in the long run.

I don't use RPGMaker because I didn't care for Ruby and afaik, they still use it as the scripting language.