Flask 1.0 Released • Hacker News Board

Re: Flask 1.0 Released

#181

Post by ddorian43 » Sat, Apr 28, 2018, 12:11 AM UTC

bobwaycott wrote: post #179

ddorian43 wrote: post #29

Earlier quoted context omitted.

Django has nicely integrated components, but each of flask components are better (jinja2, sqlalchemy, migrations, etc).

Those aren’t Flask components. They just work well with Flask. And Jinja, SQLAlchemy, and Alembic just happen to be the largest and best of them. Many of these independent components pale in comparison to their Django counterparts in glaring ways—they are often a pain to use, with some pretty questionable internal code choices. They remain used because they are often the only choice out there, even though their imple…

They are flask components cause they work well with flask and work bad with django.

Parts that I mentioned are (or were when I compared) light years ahead (especially sqlalchemy).

Re: Flask 1.0 Released

#182

Post by JoshMnem » Sat, Apr 28, 2018, 12:47 AM UTC

kstrauser wrote: post #166

JoshMnem wrote: post #156

Earlier quoted context omitted.

You don't need Django's ORM, templates, and admin section to build a Django app. Check out this example of a single-file Django project: https://www.safaribooksonline.com/library/view/lightweight-d... It's from a good book called Lightweight Django .

But if you’re not using those things, why Django?

You can use what you need and replace the rest. Or use Flask or something else. I'm not arguing for one or the other, but just mentioning that you don't need all of those mentioned conditions for Django.

Re: Flask 1.0 Released

#183

Post by setr » Sat, Apr 28, 2018, 12:49 AM UTC

donarb wrote: post #168

rrcaptain wrote: post #162

Earlier quoted context omitted.

Some frameworks however are much better at forcing you to make good design decisions. PHP is absolute garbage at that for example.

PHP is a language, not a framework.

A language is a framework, just even bigger ;)

Hell, some frameworks even come with their own (DS)Language

Re: Flask 1.0 Released

#184

Post by bobwaycott » Sat, Apr 28, 2018, 2:23 AM UTC

ddorian43 wrote: post #181

bobwaycott wrote: post #179

Earlier quoted context omitted.

Those aren’t Flask components. They just work well with Flask. And Jinja, SQLAlchemy, and Alembic just happen to be the largest and best of them. Many of these independent components pale in comparison to their Django counterparts in glaring ways—they are often a pain to use, with some pretty questionable internal code choices. They remain used because they are often the only choice out there, even though their imple…

They are flask components cause they work well with flask and work bad with django. Parts that I mentioned are (or were when I compared) light years ahead (especially sqlalchemy).

I totally agree on SQLAlchemy. It’s very good. As is Alembic.

I feel like most using Flask would consider “Flask components” to be equivalent to Flask extensions—e.g., Flask-SQLAlchemy vs SQLAlchemy proper. Maybe it’s a pedantic nitpick, but I’ve never heard anyone refer to SQLAlchemy as a Flask component in 5+ years, hence my comment about the distinction. But yes, many of the Flask-compatible Python packages you mentioned are quite a joy to use.