[Mizza]

This is really, really cool. Thanks for making this.

I really dig the Flask project (love the website and the docs, and everybody who uses it raves about it) and I hope to play with it more in the future, but I don't think I'd recommend it to somebody who is a first timer, largely because of one issue: Data. Flask leaves you to sort it out on your own, which is great if you're capable of that, but Django holds your hand, which is more appropriate for a beginner.

[akavlie]

Data? Can you explain that? Not sure what you mean.

[anthonyb]

I'm pretty sure he means that there's no database support built in, ie. you need to go download something like SQLAlchemy, SQLObject, Storm, etc. If you're already going to do that anyway it's not so much of an issue, but for people who are just getting their feet wet, it's yet another obstacle to overcome.

[akavlie]

Ah, of course.

And it makes sense -- I think Flask is a much easier introduction to config and the VC of MVC development... but once you get to the M, well... SQLAlchemy is great, but the learning curve is steeper. And even though Flask has a well-documented extension for that, it's still another package and a separate piece of documentation.

[Acorn]

I think Mazzo is referring to a lack of Django's ORM.

[jamesgeck0]

As a first-timer, I really appreciated having Flask around. It might not have a database layer, but it did have really excellent documentation. I felt like I had a much firmer understanding of what was happening with Flask than I did with Django.