Web Development

3434 readers

2 users here now

Welcome to the web development community! This is a place to post, discuss, get help about, etc. anything related to web development

What is web development?

Web development is the process of creating websites or web applications

Rules/Guidelines

Follow the programming.dev site rules
Keep content related to web development
If what you're posting relates to one of the related communities, crosspost it into there to help them grow
If youre posting an article older than two years put the year it was made in brackets after the title

Related Communities

Wormhole

[email protected]

Some webdev blogs

Not sure what to post in here? Want some web development related things to read?

Heres a couple blogs that have web development related content

https://frontendfoc.us/ - [RSS]
https://wesbos.com/blog
https://davidwalsh.name/ - [RSS]
https://www.nngroup.com/articles/
https://sia.codes/posts/ - [RSS]
https://www.smashingmagazine.com/ - [RSS]
https://www.bennadel.com/ - [RSS]
https://web.dev/ - [RSS]

Credits

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

[email protected]

Quart Vs Flask (programming.dev)

submitted 3 months ago by [email protected] to c/[email protected]

2 comments fedilink hide all child comments

Hi,

I've read quite few articles about Flask Vs quart.

But the one that I found do not go deep.. :/ (and are big adept of copy/past ...)

So, beside the extra features (ASGI, HTTP/2, WebSockets..)

I'm wondering if async/await in this context give a real boost of performance ?

When a client connect to a worker I don't think that while await, will allow another client to use the same work ? or am I wrong ?

Do you have any metric ? Or if you switched from Flask to Quart di you noticed a gain ? lost ?

Thanks.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 3 months ago

A few months ago I evaluated Quart to see if it would be a better option for https://piefed.social. It was easy to port my code from Flask to Quart and everything was mostly working within an hour or two. In the end I decided not to proceed with Quart because the performance gains only happen when there are many concurrent users and that time might never come. However the extra complexity and potential for problems was there immediately, so I just stayed with trusty old Flask. It's good to know that switching to Quart is straightforward if I need it in the future.