Ask HN: Django vs. Rails, strengths and weaknesses?
Would love to hear from people who have built something in both.
4 comments
After many years, I tried Django again and it has left me quite cold. Both Rails and Laravel have more tools to be productive.
In both Rails and Laravel, with a couple of commands you generate all the code to have the authentication system (frontend included), in Django you have to write it yourself (how many millions of times has this part been written? Does the world need you to do it again?).
Scaffolding: Both Laravel and Rails have tools to generate the code for a simple CRUD, Django does not.
In both Rails and Laravel, with a couple of commands you generate all the code to have the authentication system (frontend included), in Django you have to write it yourself (how many millions of times has this part been written? Does the world need you to do it again?).
Scaffolding: Both Laravel and Rails have tools to generate the code for a simple CRUD, Django does not.
Valid points! I basically copy over my auth templates and tweaks from one project to the next but it should be a basic working auth out of the box (unstyled templates).
I think all are great frameworks and you can accomplish equally great things. I have not used Rails other than playing around but have built large systems in (many) PHP frameworks and Django.
For me it came down the simple fact that I prefer coding in Python over Ruby or PHP.
For me it came down the simple fact that I prefer coding in Python over Ruby or PHP.
Sorry, Have you considered rust ?