6 ms·
Forget rails. Move to Django ;)
by mundanevoice 12y ago
Forget rails. Move to Django ;)
- davidw 12y agoDjango has basically the same architecture as Rails, so it's really in the same boat from that point of view.
- federico3 12y agoMinus the security issues.
- biokoda 12y agoAnd equally bad at concurrency.
- mpdehaan2 12y agoI don't buy this, having written and dealt with a lot of concurrent Django apps - I think people read something about the GIL often, and don't understand what the articles are really meaning. Basically Django is usually fronted with mod_wsgi and you use celery for backend tasks. The multiple requests part are dealt with because the web server pre-forks, and it's just fine with it. I think Django's problem is it moves very slowly, and mostly just that. The ORM isn't awesome, but it's workable. You can also choose to not use parts of it, like templates, and that's common in single-page apps.
- wldcordeiro 12y agoIt's speeding up development lately, 1.8 came out rather fast but it seems like the Django team likes to have ~1 year development cycle.
- mundanevoice 12y agoExactly, the development pace has been amazing and it is going in the right direction.
- mundanevoice 12y agoIt is not very difficult to plug in gevent/tornado/twisted with Django and deal with it in a pretty effective way. Also, most the resource memory intensive tasks are delegated to celery anyways.
- techpeace 12y agohttp://www.cvedetails.com/product/18211/Djangoproject-Django.html http://www.cvedetails.com/product/18211/Djangoproject-Django...
- mundanevoice 12y agoNot really the same architecture. It has it own differences and has much less magic involved. The project direction and the community is determined more by the community and not by a BDFL.