Hey, sorry about this but… I meant to reply to that other “this is how it’s done in math” comment, not you. I agree with you in that Rails‘ Fat Models isn’t great, and I think coupling business logic with persistence was a mistake. In general I would say that ActiveRecord is not great. It’s “adequate for some usecases”.
Going full “pure functions all the way”, is where I think we’re hitting diminishing returns - the the gap between what the language says and what the machine does needs some sort of bridge. In Haskell, the bridge is a whole host of abstractions: Monads, endofunctors etc. That’s… too much stuff. I can’t say it better, I’m afraid.
Going full “pure functions all the way”, is where I think we’re hitting diminishing returns - the the gap between what the language says and what the machine does needs some sort of bridge. In Haskell, the bridge is a whole host of abstractions: Monads, endofunctors etc. That’s… too much stuff. I can’t say it better, I’m afraid.