Re:Django vs. Flask for a long-term project
by poulsbohemian on Thursday January 23, 2014 @12:22PM
(#7109523)
I actually have the same sensation, only for me it is about how much faster I could crank out a solution if I was using Flask or Tornado. Django is probably fine for proof-of-concept style applications within a certain set of requirements, but too often it gets used for applications beyond its scope.
Re:Django vs. Flask for a long-term project
by wldlyinaccurate on Wednesday January 22, 2014 @04:43PM
(#7105570)
I've had similar experiences with Ruby - I used Sinatra to write a really simple REST API, and while getting the core stuff working was relatively simple, there were many times towards the end when I wished I'd just written it in PHP.
Oh, and don't even get me started on deployment.
Re:Django vs. Flask for a long-term project
by TylerE on Wednesday January 22, 2014 @04:52PM
(#7105621)
PHP deployment gets really painful at decent scales. The process model is very poor leading to both high memory usage and high server load.
Re:Django vs. Flask for a long-term project
by jbeja on Wednesday January 22, 2014 @05:04PM
(#7105692)
How?
Re:Django vs. Flask for a long-term project
by TylerE on Wednesday January 22, 2014 @05:17PM
(#7105759)
Because basically the interpreter starts from square one on each request. While some things can be held over (e.g. db pconnects) it's far from ideal.
Unfortunately for me, the most memorable part of the experience was repeatedly calculating how many times I could have coded the exact same solution in PHP in the time it took me to finish a Flask project.