Live data from Hacker News

Hyperflask – Full stack Flask and Htmx framework

hyperflask.dev

131–140 of 160 posts

Re: Hyperflask – Full stack Flask and Htmx framework

#132

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 mo…

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

Re: Hyperflask – Full stack Flask and Htmx framework

#133
post #124
post #17

Hello, 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!

I’ve been looking for something like this but backend agnostic (library rather than a framework) because we’re already about a million lines deep into a Django project. Anyway to lift this up into something that I can just mount into a Django app?

Some of the sub-projects of hyperflask can be re-used elsewhere but most of it is Flask specific.

Notable sub-projects that could be used with Django:

- https://github.com/hyperflask/jinja-super-macros

- https://github.com/hyperflask/jinjapy

Re: Hyperflask – Full stack Flask and Htmx framework

#134

I have been using htmx to build a web app and came to the conclusion that it is a dead-end. The main problem is that the state of your frontend application is in the URL. This is not flexible enough for modern UI where you might have many different zones, widgets, popups, etc. that all need their own local navigation, activation states etc. Putting all of this in a single global url is extremely hard. Designing your…

have you tried a native language with a networking and gui library to achieve the same thing?

Re: Hyperflask – Full stack Flask and Htmx framework

#136

Earlier quoted context omitted.

> The main problem is that the state of your frontend application is in the URL. There are plenty of ways to maintain state, including server store, sessions, localstorage, cookies, etc. Say you want the user to be able to customize the app layout: that doesn't need to be in the URL. Now say you provide a search functionality where the user can share the results: now your search criterias definitely should be in the…

> There are plenty of ways to maintain state, including server store, sessions, localstorage, cookies, etc. Say you want the user to be able to customize the app layout: that doesn't need to be in the URL. Now say you provide a search functionality where the user can share the results: now your search criterias definitely should be in the URL. > It's not a black or white, one actually has to think about what the appl…

> You don't have to do any of this in a Vue / React app

Something has to do this in an app regardless of what UI framework you're using. Deciding where a particular piece of state lives is fundamental to web development, and yes, URL/session/cookie/database are all valid options depending what kind of state you're storing.

Re: Hyperflask – Full stack Flask and Htmx framework

#137

Earlier quoted context omitted.

> The main problem is that the state of your frontend application is in the URL. There are plenty of ways to maintain state, including server store, sessions, localstorage, cookies, etc. Say you want the user to be able to customize the app layout: that doesn't need to be in the URL. Now say you provide a search functionality where the user can share the results: now your search criterias definitely should be in the…

> There are plenty of ways to maintain state, including server store, sessions, localstorage, cookies, etc. Say you want the user to be able to customize the app layout: that doesn't need to be in the URL. Now say you provide a search functionality where the user can share the results: now your search criterias definitely should be in the URL. > It's not a black or white, one actually has to think about what the appl…

User state is sometimes necessary, but frequently a crutch to avoid answering the real questions. Much of the time, this user-state is at the core of many performance and behavior issues as the user is burdened with unnecessary DOM reorganization. If the layout is dependent on more than just URL parameters and simple server state/cookies, then it begs the question: does this page really have a specific, well-defined purpose? If not, it's ripe for noisy UX, confused users and hard to untangle interface bugs. If so, you probably shouldn't be doing so much on-the-fly DOM configuration. You're not building an OS or window manager here.

Notably, none of this is incompatible with React/Vue where you need it.

Re: Hyperflask – Full stack Flask and Htmx framework

#138
post #72
post #36

Earlier quoted context omitted.

It's a dead end for your use case, let's be very clear about that. And it's funny that you think anything about React and/or Vue is 'trivial'.

Surely you’re not saying the frameworks famous for ui = f(state) actually suck at managing state…

If it only were true. React is nothing like ui = f(state). More like ui = f(some_trivial_state) + lifecycles magic + probably global_state.

Garbage. But effective devrel.

Re: Hyperflask – Full stack Flask and Htmx framework

#139

I have been using htmx to build a web app and came to the conclusion that it is a dead-end. The main problem is that the state of your frontend application is in the URL. This is not flexible enough for modern UI where you might have many different zones, widgets, popups, etc. that all need their own local navigation, activation states etc. Putting all of this in a single global url is extremely hard. Designing your…

> This problem is trivially solved by React / Vue that all provide their version of a state store that can hold the state

What exactly are you talking about, for React? What provides "a state store"?

Re: Hyperflask – Full stack Flask and Htmx framework

#140
post #43

Earlier quoted context omitted.

There isn't any real inherit project structure. Opinionated frameworks often work better with multiple people involved.

Isn't every project an ad hoc opinionated framework? You can do code reviews etc to get some alignment and not have everyone working against each other.

No, every project certainly isn't opinionated. There are a lot of approaches you can take to get there but I wouldn't recommend discussing alignment after the code is already written and trying to get large groups to agree.
Post reply on HN