WHYYYYYYYYY.

[allixsenos]

[pizzapanther]

I don't get it what's the purpose? I'm just super curious and wondering what I'm missing here.

[channprj]

It feels like hybrid creature in StarCraft 2 for me... But quite interesting and I'll keep eye on this. :speak_no_evil:

[kennethreitz]

because django's best parts are the admin and the ORM. Flask is superior for everything else, in my opinion.

[yokotoka]

@kennethreitz

because django's best parts are the admin and the ORM

Best part of Django is ORM? ORM?!?!?!

Did you saw sqlalchemy?

[wowkin2]

django's best parts are the admin and the ORM

just leave it here: https://flask-admin.readthedocs.io/ http://docs.sqlalchemy.org/

[krnr]

from a sideview I can support the creator: Alchemy is really good, but ORM is not THAT worse. It's cohesive, powerful and fast if you use it correctly. So I can understand his choice. I'd rather hear the pro's of using werkzeug as midleware system, because django midleware is really its bottleneck. And, yes, it's a very interesting idea and i'm also curious

[adrianiskander]

Hybrid like this may seem funny at first place but its assumptions are reasonable. Some arguments:

• Flask has better template engine (Jinja)
• Flask imports are more intuitive (from flask import x,y,z)
• views/api prototyping is faster, easier and more fun (no excessive setup)

On the other side:

• Django has better migration engine (it allows to migrate constraints)
• Django ORM is easier to use (SQLA is packed with features but its docs are tough)
• No problem with shuffling models across app and write tests (no app context issues)

So crossover like this would be:

• Flask-like views/routes/api (things that Flask excels out of the box)
• Django-like models, migrations, admin, tests (thing that Django excels out of the box)

Thanks for this interesting setup. I'll experiment with it and see if the world ends.