4 ms·
I've been using Django for a lot of projects, but have recently converted to Rails 3 for a personal project. What I like about Rails is that plugins are mostly
by bad_user 16y ago
I've been using Django for a lot of projects, but have recently converted to Rails 3 for a personal project.
What I like about Rails is that plugins are mostly pieces of infrastructure, not ready-to-use mini-applications that are hard to customize. And Rack plugins (pieces of middleware, done in a standard/reusable way, contrary to Django's middleware) are just awesome.
I also like about Rails that authentication and admin are not built-in. Lots of plugins available for a quick-and-dirty job anyway.
I also like that defining models and even querying has been abstracted away in different interfaces, and that you can use MongoDB in a similar way as you would use a relational database.
Also, in case you need to decouple the request validations from the models (i.e. forms in Django) without HTML-rendering logic attached (useful at times, but completely getting in your way once you try doing anything complicated); in Rails you can, and it looks and feels cleaner because the field types don't have to be related to stuff you're rendering in the HTML response (i.e. field = forms.MultipleChoiceField(widget=CheckboxSelectMultiple)).
Django is awesome in case you ever thought about using Drupal for a project: much more flexible and dev friendly. But it completely got in my way so many times that I actually thought about writing my own Python web framework; which I shouldn't because people have been working on web-related stuff for the past 20 years.
- jasonwocky 16y ago>And Rake plugins (pieces of middleware, done in a standard/reusable way, contrary to Django's middleware) are just awesome. I think you mean Rack plugins (noted b/c Rake is something entirely different in Ruby parlance).
- bad_user 16y agoYes, thanks: it's a common misspelling that I make.
- mickeyben 16y agoAnd Rake plugins (pieces of middleware, done in a standard/reusable way, contrary to Django's middleware) are just awesome. I think you're talking about rack middlewares. Rake is the Ruby make.
- zeemonkee 16y ago> But it completely got in my way so many times that I actually thought about writing my own Python web framework; which I shouldn't because people have been working on web-related stuff for the past 20 years. You could always try Flask or Pylons.
- didip 16y agoPylons is in maintenance mode, Pyramid is succeeding it.
- parfe 16y agoPylons is dead. The authors moved on to Pyramid after declaring Pylons core too difficult to maintain. The upgrade path to Pyramid is "Run your pylons app inside pyramid as you rewrite it from scratch [into our new shiny framework we promise not to abandon]!"
- code_duck 16y agoYou're not forced to use the Forms class in Django. You can process and output forms manually; that part never felt natural to me so I just skipped it and work with them like I do in PHP.
- itsnotvalid 16y agoAgreed that things like forms in django really steps in when more customization is needed. You with have it useful for you or you need to completely throw the whole stack away. In rails you can have them separated and just use a bit of the magic (well rails used to have the magical prototype + script.aculo.us, but they managed to rip that away)