[gls2ro]

Can you please explain your opinion?

I am curious of two things:

1. How come Django is not legacy but Rails is?

2. How come Rails in itself it legacy for SSR?

I am curious and I think it worth explaining as it might be that people read the comments here and do not understand what criteria did you considered when deciding which is which.

[yamellasmallela]

Django uses a modern language and is simple

Rails is not sanely organized, very complicated, and ruby is just a crazy language

[midrus]

This is your purely subjective opinion.

I've worked with both profesionally, and my also purely subjective opinion is that while Ruby is better than Python, Rails is thousands of miles ahead of Django.

On the Ruby side, the standard library is a lot more consistent, the language itself is more powerful, the tooling is better (bundler + gems + rake vs pip..oh, wait its poetry.. or was it pipenv), puma is objetively better than uWSGI (no releases in years) and gunicorn (can't serve static files! wtf!).

Rails provides an opinionated and clear way to do frontend too (better templates, stimulus, hotwire, etc) and a way to do websockets, an official one. Translations in rails are a lot better too, based on keys instead of on 80's gettext funkyness. Routing is a lot easier too, just map urls to controllers... in django do you do function views? or class based views? now that's a mess. The "asyncification" going on in django is CRAZY, the complexity they're adding is React level insane.

Also, ruby didn't break the ecosystem and f*d half the community like python did from 2->3 (that's when I gave up on it) and nor is doing it with all the async madness in python splitting again the ecosystem on things that support it vs things that don't.

The only thing I miss from django is the migrations system, which I think are better than in rails, and maybe django-rest-framework.

So, there you go... your subjective opinion vs mine, everyone has one.