Thanks for the advice. I had built out a small application in dotnet core mvc and rails to get a taste of how both of them are currently structured. Rails OOP

Thanks for the advice. I had built out a small application in dotnet core mvc and rails to get a taste of how both of them are currently structured. Rails OOP and dynamism allows for some less verbose abstractions which I like (I'm not afraid of the magic, the rails source seems pretty legible), but dotnet MVC has some nice things like async built in, and feature-full job queueing without paying $1k per year. Those are my initial impressions. I'd be glad to update my knowledge if I'm wrong.