IMHO if you like static types, I suspect you won't like Rails. Its the intentional opposite of them in many ways. I made the swap you're contemplating with simi

IMHO if you like static types, I suspect you won't like Rails. Its the intentional opposite of them in many ways. I made the swap you're contemplating with similar reservations and absolutely regret it. Rails is definitely great but IME it appeals to a particular kind of developer, in the same way hard-core functional languages, strict types, or e.g. Go's' flavor of error handling each appeal to other groups. I've found those higher level patterns extend beyond mere fashion and more into some kind of persistent style preferences that's not easily changed. I dipped into the functional world and did not like it. Now I feel similarly about Rails. There are just so many times I want to offload my mental model into types, and that concept doesn't really exist in Rails. And it doesn't seem to bother most of the folks I work with, and I suspect it has more to do with how my brain works under the hood compared to theirs. I definitely think Rails can be worth trying, but if you're the type to be evaluating types from the outset, I'd wager that's the exact kind of person that won't like what they get into.