Rather than quibbling over syntax, I'd like to comment on a real concern I have about blogs, particularly ones that engage in hagiographies on things they don't appear to rightly understand.<p>Nota bene: I am a user of Flask and have been one for quite some time. I am incredibly fond of it and it has replaced Django for most things I do in web dev. I am very familiar with it and its limitations/ugly corners. Familiarity breeding contempt and all that. That said, little contempt has arisen from my familiarity with Flask. It's that good.<p>Do we upvote these blog posts because we think they're constructive? This is somewhere on the order of a press release in depth. The farthest this post gets is in describing an app that uses hard-coded credentials to log an administrator in.<p>This doesn't demonstrate the strengths of Flask, nor the weaknesses, nor why it's necessarily better than Sinatra, Bottle, or any other micro web-framework.<p>Since this post has failed to do so, I'll fill in that gap as quickly as I can.<p>Flask is great because it <i>scales</i> to your needs. It starts as painlessly as any other micro web-framework, but what makes it nice is that it's so <i>easy</i> and <i>clean</i> to graft disparate ways of doing a web-app.<p>In my particular case, I'm in the process of building a service on Flask and MongoDB. I'm in the process of making Flask, WTForms, and MongoEngine all play nice together and Flask has done a wonderful job of making this painless because it doesn't make any bizarre assumptions and it doesn't force any strange contortions in my code like Sinatra or raw Rack apps do.<p>Having hacked on some Rack and Sinatra code, I can tell you right now that the moment you want to make a "real" app with the typical complexity of a mature service, even the bare basics get <i>painful</i> really fast.<p>Flask hasn't done this to me yet, it's already breezed well past where I've taken raw Rack and Sinatra+Rack apps before.<p>This blog post, however, does not come from experience. It does not attempt to explain why Flask is better than the alternatives, it doesn't even demonstrate any interesting aspects of Flask.<p>This is blogspam.<p>Please reconsider your upvotes, please reconsider promoting content like this again.<p>Popularity for popularity's sake in the absence of knowledge, experience, and data is simply "pop culture". (cf. Node.js)<p>Edit: Worse, the author even explicitly appeals to the quality of Flask on the basis of "branding".<p>Engineering decisions shouldn't be made on the basis of pop culture.<p>Choose Flask because you know it suits the problem you're solving well, or because you know it suits your style of programming.<p>Don't choose it because somebody showed you a "hello, world!" example.