I don't know anything about Rails but after having built a fairly large production web app with Django about a year ago, nothing about it felt cutting-edge to m

I don't know anything about Rails but after having built a fairly large production web app with Django about a year ago, nothing about it felt cutting-edge to me: - Async support was second class back then, not obvious how to implement fully. - REST APIs are a library add-on instead of first-class. An excellent library, but still. - The package ecosystem sometimes reminded me of the wild-west that is Node.js - Dependency management is a complicated story (arguably caused by Python, rather than Django itself) - Django Models are cool and expressive, but nowadays I would rather express my models in something like a dataclass, or a Pydantic model, or just a regular class... Maybe Rails has these problems and more, I don't know. I'm not saying I'm never going to use Django again, but there's a large chance I will look elsewhere for a batteries-included framework next time I need one.