His major arguments seem to be that he doesn't like ruby's name.
My theory is if the author was in anyway correct in his assertions he wouldn't bother to write hit peices like this. He'd just move on.
The fact that people get stuff done in Ruby and that Ruby is constantly improving acts as a strong counter argument.
My first programming language was BASIC. My second programming language was assembly (for Z80A, then for 6502, later for x86). My third programming language, the one the author would call "formative" was Pascal.
None of these languages left me "imprinted" to the point of forever shaping my tastes and making me unable to adapt to or appreciate newer languages.
In fact, if we're talking about formative experiences, I remember one professor at the university who said, quite seriously, that "Anyone who has programmed in BASIC has been damaged for life and will never be a good programmer." The reason why that was a formative experience is that it taught me that people in which we put our trust can be assholes who ruin people's lives because they think some bit of dogmatic bullshit they came up with is clever.
And that's really what the article is about: the author wants to show off how clever they are. I'm okay with that, in general. I remember reading Steve Yegge's blog posts and finding them entertaining, regardless of whether I agreed with them. Thing is, Yegge had a lot more to say than just "look at how clever I am".
That was peak Wired: techno hippies in Prague, the new year "scared shitlist" (President Dole... President Gates!), TV watches you, General Magic, Ricochet radio modems (the very first wifi), and it still had much more of a "moody b&w" aesthetic than the dayglo nightmare that was to come.
https://james-iry.blogspot.com/2009/05/brief-incomplete-and-...
What a horrific piece of journalism. This reads like something a struggling journalist would put out after a few hours with ChatGPT.
My guess is the first Ruby codebase he worked on was a particularly bad codebase that didn't conform to Ruby standards.
No, let's talk about an N=1 example of performance issues _from 15 years ago_, on version 1 of the language, where I'll bet my house that the biggest issue was poor usage of Rails ORM and architecture and not the Ruby language itself.
Cool.
mikece•2mo ago