When I speak about what I intend to do (that being avoiding being a passenger in a Toyota vehicle henceforth) "I have no idea what I'm talking about"?
Huh. Next you'll be telling me I don't know what my name is or where I live.
Or perhaps you meant that my life-long 20+ year career as a software developer had left me unable to assess the development failures outlined in this article.
I honestly didn't care enough to spend time looking into it as I'm not being paid to make Wired's website functional. Thankfully, BrikoX was the real MVP and ensured nobody has to actually go there to access the content by posting an archive link.
It’s about ending the compulsory theater where effort is only recognized if it fattens a ledger. It’s about admitting that tying basic dignity to wage labor was always a barbaric hack, only tolerated because we lacked the tools to do better.
Cool, in isolation I'm all for it. Now explain how we're going to transform society to channel a significantly larger amount of privatized profits into paying for the things people need to, you know, live.
That's a little like saying that you'd rather be shot in the head than burned alive. Sure, I won't argue against it, but I've got a better suggestion: How about neither?
Disclaimer: I'm not Ruby programmer. I evaluated it once, saw no particular reason to use it instead of Python and promptly forgot about it.
With that said, the specific criticism(s) are:
Poor performance. Sure. Ruby does appear to be somewhat slower than Python, but I'm more concerned about the peak memory consumption which is admittedly frequently pretty terrifying. Mind you, if I need high performance, I'm not likely to be using either Ruby or Python. It's fine for automation scripts, rapid prototyping or experimentation, hypothesis validation, moderate data processing, analysis and visualization, but yes: If you build your (supposedly) hyper-scalable website on Rails or use it for the system software for your embedded device, you're going to have a bad time. Every tool has its place (except Brainfuck). Don't use a hammer when you should be using a screwdriver.
The above also covers the railing against rails, about which I have no further comment as I've never used it. Maybe it's nice, but if you're working on something with more concurrent users than your homelab automation UX, there's undoubtedly better alternatives.
...And that appears to be it. So it boiled to down to "performance". Does that in and of itself make Ruby "not a serious programming language". Well, if it does, then the same applies to Python. Does it mean that there's probably a better alternative for any given application? Probably yes.
That looks like what'd happen if one put APL in a blender. I don't know who came up with whatever that is, but they need to get outside more. Or, you know, just once maybe.
When I speak about what I intend to do (that being avoiding being a passenger in a Toyota vehicle henceforth) "I have no idea what I'm talking about"?
Huh. Next you'll be telling me I don't know what my name is or where I live.
Or perhaps you meant that my life-long 20+ year career as a software developer had left me unable to assess the development failures outlined in this article.
Wow. Thanks.