News for hackers. Stuff that matters.

A comment on Hyperflask – Full stack Flask and Htmx framework. Parent comment

Re:Hyperflask – Full stack Flask and Htmx framework by andersmurphy on Thursday October 16, 2025 @04:58PM (#45610590)
Correct. That's literally what happens with the scroll position, and share modal in this demo (QR code is generated on the fly on the backend):

https://checkboxes.andersmurphy.com

[ Parent | on HN ]
Re:Hyperflask – Full stack Flask and Htmx framework by julianz on Thursday October 16, 2025 @09:25PM (#45612488)
300ms of latency to click a checkbox is a horrible experience, though.
[ Parent | on HN ]
Re:Hyperflask – Full stack Flask and Htmx framework by christoff12 on Friday October 17, 2025 @03:41AM (#45614197)
not really in this case
[ Parent | on HN ]
Re:Hyperflask – Full stack Flask and Htmx framework by andersmurphy on Friday October 17, 2025 @07:32AM (#45615483)
Feels surprisingly good to me.
[ Parent | on HN ]
Re:Hyperflask – Full stack Flask and Htmx framework by andersmurphy on Friday October 17, 2025 @07:07AM (#45615311)
Not sure why this is getting downvoted. I'm literally showing an example of storing popup state in the database as per the parents question.

> You mean I should be storing the state of a popup menu in my database?

[ Parent | on HN ]
Re:Hyperflask – Full stack Flask and Htmx framework by b_e_n_t_o_n on Saturday October 18, 2025 @05:10PM (#45630369)
There is a noticeable delay between interaction and response (~200ms), which is way over the usual 16ms budget for smooth interactions. I think you need some pending state on the client, but that sort of breaks the idea of storing all state on the server haha.
[ Parent | on HN ]