I can’t speak to Rust, but these past 6 months I’ve had a very interesting adventure diving into Ruby on Rails. My background is full stack JS dev with Typescript. So I like my shit explicit written out, no magic. I like my shit strongly-typed. And I like my shit running primarily on the front-end.
Well I had several sour run-ins with Ruby on Rails and I had decided that it was the worst thing ever and I hated it. And I valiantly defended that position for many years. However, recently I’ve had several roles that required me to use Rails in various ways and I managed to find one or two things that I found… interesting… about it.
So I decided I was going to learn Ruby on Rails just so I could see what all the fuss was about and then I could _know_ I was right and throw it in all those smug Ruby-ist’s faces!
Long story short, I’ve learned a great deal and I’ve come to appreciate many of the design decisions that Rails has made over the years. It’s very opinionated which can go either way, but what it sets out to do, it does very well. I am actually building a Rails application using turbo and it’s been mind-expanding and a total joy to use.
To that end, I can only recommend going in to “prove yourself right” and you may find that you prove yourself wrong.
I still hate Ruby as a duck-typed, dynamic language. I will jump ship at the first full stack web framework that is as comprehensive as Rails but has full-stack, native Typescript runtime. (Hoping for some deno project to fill that void!)
But until then, I’ve come to appreciate and even enjoy Rails.
Well I had several sour run-ins with Ruby on Rails and I had decided that it was the worst thing ever and I hated it. And I valiantly defended that position for many years. However, recently I’ve had several roles that required me to use Rails in various ways and I managed to find one or two things that I found… interesting… about it.
So I decided I was going to learn Ruby on Rails just so I could see what all the fuss was about and then I could _know_ I was right and throw it in all those smug Ruby-ist’s faces!
Long story short, I’ve learned a great deal and I’ve come to appreciate many of the design decisions that Rails has made over the years. It’s very opinionated which can go either way, but what it sets out to do, it does very well. I am actually building a Rails application using turbo and it’s been mind-expanding and a total joy to use.
To that end, I can only recommend going in to “prove yourself right” and you may find that you prove yourself wrong.
I still hate Ruby as a duck-typed, dynamic language. I will jump ship at the first full stack web framework that is as comprehensive as Rails but has full-stack, native Typescript runtime. (Hoping for some deno project to fill that void!)
But until then, I’ve come to appreciate and even enjoy Rails.