Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Flask 1.0 Released

palletsprojects.com

Post reply on HN
Print view View original

31–40 of 184 posts

Re: Flask 1.0 Released

#31

Post by devy »

nickjj wrote: post #28

Flask has a stigma for not being that good when building larger apps, but honestly Flask scales really well for that type of use case (coming from a development / maintenance point of view). I have some pretty large Flask apps with dozens of top level dependencies and models spanning across many thousands of lines of code. Even if I don't touch the code base for a few months, it's easy to jump back into it. I'm also…

> Flask has a stigma for not being that good when building larger apps

Not sure how to quantify that "large" but I've worked on some api backend services written in Flask with a quarter million lines of python code and not feeling "outgrowing" Flask. Granted, it took some good design and effort to make all piece s work together. These days, horizontally scale apps is the way to go.

Re: Flask 1.0 Released

#32

Post by danielhochman »

BerislavLopac wrote: post #7

I understand that Flask has become popular because it is easy to learn, but my experience is that as your knowledge progresses it just keeps getting in your way. I particularly dislike some design choices which look like afterthought hacks, such as global variables for current request and using abort() functions instead of raising exceptions directly. EDIT: To avoid hollow naysaying, here are some alternatives to Fla…

It is possible to register error handlers for exceptions in Flask. See http://flask.pocoo.org/docs/1.0/patterns/apierrors/.

Re: Flask 1.0 Released

#33

Post by hultner »

devy wrote: post #31
nickjj wrote: post #28

Flask has a stigma for not being that good when building larger apps, but honestly Flask scales really well for that type of use case (coming from a development / maintenance point of view). I have some pretty large Flask apps with dozens of top level dependencies and models spanning across many thousands of lines of code. Even if I don't touch the code base for a few months, it's easy to jump back into it. I'm also…

> Flask has a stigma for not being that good when building larger apps Not sure how to quantify that "large" but I've worked on some api backend services written in Flask with a quarter million lines of python code and not feeling "outgrowing" Flask. Granted, it took some good design and effort to make all piece s work together. These days, horizontally scale apps is the way to go.

That sounds like a helleva large codebase, especially for Python.

What did the application do? How large was the dev team?

Re: Flask 1.0 Released

#34

Post by citilife »

ckuhl wrote: post #13
BerislavLopac wrote: post #7

I understand that Flask has become popular because it is easy to learn, but my experience is that as your knowledge progresses it just keeps getting in your way. I particularly dislike some design choices which look like afterthought hacks, such as global variables for current request and using abort() functions instead of raising exceptions directly. EDIT: To avoid hollow naysaying, here are some alternatives to Fla…

The real value of Flask is that it makes you appreciate what Django does by default. When I first started learning Python / web frameworks, I went with Flask because it was smaller and "simpler". As my project grew however, I had to organize it. I was basically imitating what Django gives you by default, though less cleanly.

Both Django and Flask make me yearn for Rails :(

Re: Flask 1.0 Released

#36

Post by qudat »

ckuhl wrote: post #13
BerislavLopac wrote: post #7

I understand that Flask has become popular because it is easy to learn, but my experience is that as your knowledge progresses it just keeps getting in your way. I particularly dislike some design choices which look like afterthought hacks, such as global variables for current request and using abort() functions instead of raising exceptions directly. EDIT: To avoid hollow naysaying, here are some alternatives to Fla…

The real value of Flask is that it makes you appreciate what Django does by default. When I first started learning Python / web frameworks, I went with Flask because it was smaller and "simpler". As my project grew however, I had to organize it. I was basically imitating what Django gives you by default, though less cleanly.

I disagree. With any sufficiently complex project, Django's batteries included got in the way whereas scaling Flask felt smooth.

Re: Flask 1.0 Released

#37

Post by theptip »

BerislavLopac wrote: post #7

I understand that Flask has become popular because it is easy to learn, but my experience is that as your knowledge progresses it just keeps getting in your way. I particularly dislike some design choices which look like afterthought hacks, such as global variables for current request and using abort() functions instead of raising exceptions directly. EDIT: To avoid hollow naysaying, here are some alternatives to Fla…

Another interesting API framework from the DRF author:

https://github.com/encode/apistar

Uses Python3 type annotations to do serialization. Not sure it's ready for production, but it has some very interesting new concepts.

Also worth mentioning Sanic which is fast and I believe dispenses with Flask warts like the thread-local Request object (though it does bill itself as "Flask-like").

Re: Flask 1.0 Released

#39

Post by ageofwant »

hultner wrote: post #33
devy wrote: post #31

Earlier quoted context omitted.

> Flask has a stigma for not being that good when building larger apps Not sure how to quantify that "large" but I've worked on some api backend services written in Flask with a quarter million lines of python code and not feeling "outgrowing" Flask. Granted, it took some good design and effort to make all piece s work together. These days, horizontally scale apps is the way to go.

That sounds like a helleva large codebase, especially for Python. What did the application do? How large was the dev team?

I have worked on several Python code bases exceeding 500k lines. Not sure why you think that's uncommon.

Re: Flask 1.0 Released

#40

Post by nicodjimenez »

nickjj wrote: post #28

Flask has a stigma for not being that good when building larger apps, but honestly Flask scales really well for that type of use case (coming from a development / maintenance point of view). I have some pretty large Flask apps with dozens of top level dependencies and models spanning across many thousands of lines of code. Even if I don't touch the code base for a few months, it's easy to jump back into it. I'm also…

Flask _does_ scale really well with lines of codes. However the limitations of Python w.r.t. async log really start to show once you step beyond simple CRUD apps.
Post reply on HN