Earlier quoted context omitted.
> In reality, people ended up having to deal with weird bugs because asynchronous Python isn't the most ergonomic That is an understatement. I loathe working with async Python. > For example, people could build an API that will contact OpenAI before returning a response. That's where FastAPI truly shined because of native asynchronous views which provides better performance over Flask's async implementation. TO be fa…
> TO be fair there are lots of other things that require a response from an API before responding to the request and therefore async reduces resource usage over threads or multi-process. Agreed. However, these are rare and many people have been abusing asynchronous views instead of delegating the task to a background worker when multiple external requests are required. Showing a spinner while polling a synchronous vi…
Hyperflask – Full stack Flask and Htmx framework
21–30 of 160 posts
Re: Hyperflask – Full stack Flask and Htmx framework
#22Earlier quoted context omitted.
After using both Flask and FastAPI extensively I can attest that Flask is the better technology. Flask is extremely stable and has solid organization around them via Pallets. This is a great benefit as they are keeping the ecosystem moving forward and stable. https://palletsprojects.com/ Versus FastAPI which is lead by a single maintainer which you can search back on HN about opinions on how he's led things. Flask al…
Flask is missing... pydantic, dependency injection, openapi, swagger, real async.
https://luolingchun.github.io/flask-openapi3/v4.x/
> dependency injection
While nice I never found this to be a critical deciding factor of using a technology.
> real async
If you really want it there is Quart which is real async
https://github.com/pallets/quart
I'm not a huge async fan in python anymore so not it's not a huge issue for me. But there are definitely options for Flask if you want to use async.
Re: Hyperflask – Full stack Flask and Htmx framework
#23- Components: https://hyperflask.dev/guides/components/ - Bundling view and controller in the same file: https://hyperflask.dev/guides/interactive-apps/
I think these may be footguns though. Components for example are just a regular macros under the hood. Why not use macros then?
I'm also curious about the choice of Flask. I started with a similar approach for /dev/push [1], but ended up moving to FastAPI + Jinja2 + Alpine.js + HTMX once I figured out FastAPI wasn't just for APIs. I wanted proper async support. I love Flask, but don't you find it limiting?
Re: Hyperflask – Full stack Flask and Htmx framework
#24Re: Hyperflask – Full stack Flask and Htmx framework
#25Curious choice of backend python. Indeed Flask is a famous python framework but it seems it has been completely overshadowed by FastAPI. I would suggest "HyperFastAPI"
Is FastAPI still (micro)managed by one person?
https://www.sequoiacap.com/article/partnering-with-fastapi-l...
Re: Hyperflask – Full stack Flask and Htmx framework
#26Re: Hyperflask – Full stack Flask and Htmx framework
#27Re: Hyperflask – Full stack Flask and Htmx framework
#28Re: Hyperflask – Full stack Flask and Htmx framework
#29What is the largest app powered by this framework?
Re: Hyperflask – Full stack Flask and Htmx framework
#30Hello, author of hyperflask here. I'm happy to finally announce this project as I've been working on it for quite some time. I made an announcement post here: https://hyperflask.dev/blog/2025/10/14/launch-annoncement/ I love to hear feedback!
Would check it out asap!