News for hackers. Stuff that matters.
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.
Re:Django vs. Flask for a long-term project by rmrfrmrf on Wednesday January 22, 2014 @04:46PM (#7105584)
I think we should get started on deployment considering how often it's swept under the rug as something that the "lowly sysadmins" have to deal with.