The author (not me) says: “Right up front, I should say that Rust is very good at what it’s designed to do, and if your project needs the specific benefits of Rust (a systems language with high performance, super strong typing, no need for garbage collection, etc.) then Rust is a great choice. But I think that Rust is often used in situations where it’s not a great fit, and teams pay the price of Rust’s complexity and overhead without getting much benefit.”
A suprisingly thoughtful and detailed essay. I skimmed it. It's a bit of intellectual play because the question could be answered much more briefly. But the article does go deep and look at the question in many different interesting ways.
But I digress: objects > functions. At least in the context of getting stuff done in Ruby. This pretty much applies to most of the rest of the points in this post, so just keep that in the back of your brain.
A good list. I know every single one and would generally agree with it. Some books are too high in the list and some too low. But an excellent starting point.