4 ms·

Last week I compared RubyOnRails (RoR) and Python Django. For rapid prototyping, I think RoR has still something to say. I like Django but I see little use (c

Last week I compared RubyOnRails (RoR) and Python Django. For rapid prototyping, I think RoR has still something to say. I like Django but I see little use (correct me, if I am wrong) from big Startups. I was able to setup a tiny custom status page with RoR picking a module found on the web, and starting customizing the app for my own goals. AngularJS and React are the king on the frontend in this years, so the Django/RoR approach seems a bit "old"; nerveless on RoR guides you find a way to use RoR only as an "API" Layer, so integrating it with an Angular frontend, for instance. And with K8s and microservices, scaling is not a big issue if you code a share-nothing stack.

berkes 5y ago
My take is that Django is stronger for websites: leaning slighly more towards a selfbuilt CMS. Whereas Rails is stronger for webapps. With a large overlap, and only slightly so. But that both lack severely for complex business flows, -logic and integrations. Both are strong for CRUD cases, with accidental workflows attached to those operations. But that both lack tooling, and have the wrong architecture, to support complex, intermingled, businesslogic over time.
- cutler 5y ago
  Compared with what? Spring? ASP.Net?
  - berkes 5y ago
    Compared with "No Framework". Spring, ASP.net, Rails, Symfony, Django all follow very much the same patterns and architecture.
bodge5000 5y ago
I personally see a lot more for Django than Rails, but then again I know Django and don't know Rails (been meaning to learn it for a long time) so that could be biasing me
- cutler 5y ago
  Yes. Indeed.co.uk has had more Django than Rails jobs for a long time now but recently the gap has dropped from 70% to 30% so maybe Ruby 3/Rails 7/Hotwire has generated more interest.