3 ms·
I kinda see the point, especially as someone who's used RoR quite heavily and is currently developing code with Django. It's ultimately a tradeoff between rapi
by iuguy 18y ago
I kinda see the point, especially as someone who's used RoR quite heavily and is currently developing code with Django.
It's ultimately a tradeoff between rapid and optimised development. Both have their advantages and disadvantages.
The project I'm developing in Django would never have more than 100 concurrent users so for me, that's fine. The framework approach and lack of need to optimise gives me an advantage I otherwise wouldn't have.
I wouldn't use Django (or RoR) if I had 10s of thousands of concurrent users, not because it can't scale, but because the effort required from me in terms of optimisation starts to outweigh the benefits gained from the framework at that point.
- mrtron 18y agoLet me tell you a little secret. I convinced a large website to switch new development into Django and then we were able to do an entire site rewrite a few months later. The site gets a ton of concurrent users. The framework provides some caching mechanisms at multiple levels that makes handing that very easy.