[hunvreus]

Some interesting concepts:

- 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?

[1]: https://github.com/hunvreus/devpush

[fletchowns]

> Bundling view and controller in the same file

It reminds me of how PHP development used to be back in the day. That's not meant as a bad thing, I always liked how simple it made the development process for the right size project.

[rdedev]

I moved to Quart instead. It's flask with async support built by the same developer.

[hunvreus]

Quart was interesting, but it didn't seem to have as much traction as FastAPI. I also seem to understand Flask is trying to integrate some of Quart's ideas.

[reality_inspctr]

yeah fastapi + htmx is very effective.