Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You can always detect server side if it’s an Unpoly request, and which fragments it is asking for as that information goes in the request headers.

Or point the request to another view that just returns those fragments.

But I don’t think many apps need this level of optimizations.



I am now converting an app from htmx to unpoly. Indeed, much less attributes to write and now my app has proper browser history and full page rendering linked to this history, all with minimal effort. This is brilliant, how come I never heard of unpoly ? Thanks for pointing to it.


It has a marketing problem for sure, given how everyone loves HTMX and nobody even heard of Unpoly.

Not that I'm a fan of doing marketing of tech, but... that's the explanation I find for it.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: