Live data from Hacker News

Htmx 2.0.4 Released

github.com

21–30 of 136 posts

Re: Htmx 2.0.4 Released

#21

Earlier quoted context omitted.

> memory wouldn't survive a page refresh That isn't very common. > sessionStorage wouldn't survive a tab close When a tab is restored, the browser typically restores sessionStorage. > i'm not opposed to making the latter an option though That isn't what I was getting at. If I'm going to buy into htmx, I want to understand the design. I wondered why this was the default, and why I hadn't seen it mentioned as a securit…

i don't know how common it is or isn't, but it's reasonably common for htmx to be sprinkled into a regular MPA with full page navs, etc. and memory wouldn't survive that no strong opinions on session vs local storage, i was trying to make htmx act as much like the browser as possible and the browser caches across tabs you can disable history on any page by using the hx-history attribute and you can force a server req…

Memory would indeed be an issue for mixing MPA and SPA, but besides not being an issue for a full SPA it also wouldn't be an issue for sites that are all MPA except AJAX submissions that don't cause a SPA page change. Currently I think an all MPA would waste the localStorage space.

SessionStorage by default with prominent placement in the docs would be better I think. It would automatically clean up the data from visitors' disk space at appropriate times, whereas the localStorage setting puts it in a place that gets persisted for quite some time.

Thanks for those links, I've read them but it's good for others here to see them.

Re: Htmx 2.0.4 Released

#24
post #17

Nothing new under the sun. This is just a rip off of intercooler js. Only without jQuery. Times moved on and someone copied the idea (exactly) but with the aid of modern JavaScript didn't need jQuery. I mean it's nice that it's a bit more modern but still.

You do realize that htmx is intecooler.js 2.0? Made by the same people, for the same purpose. And if you don't believe me, the intercooler.js homepage says pretty much the same exact thing.

I think you'll find there is some animosity

https://x.com/intercoolerjs/status/1845878585078567084?t=p41...

Re: Htmx 2.0.4 Released

#26
post #24

Earlier quoted context omitted.

You do realize that htmx is intecooler.js 2.0? Made by the same people, for the same purpose. And if you don't believe me, the intercooler.js homepage says pretty much the same exact thing.

I think you'll find there is some animosity https://x.com/intercoolerjs/status/1845878585078567084?t=p41...

... you realize this is a joke right?

Re: Htmx 2.0.4 Released

#27
post #24

Earlier quoted context omitted.

You do realize that htmx is intecooler.js 2.0? Made by the same people, for the same purpose. And if you don't believe me, the intercooler.js homepage says pretty much the same exact thing.

I think you'll find there is some animosity https://x.com/intercoolerjs/status/1845878585078567084?t=p41...

It's a joke.

Re: Htmx 2.0.4 Released

#28

Earlier quoted context omitted.

memory wouldn't survive a page refresh sessionStorage wouldn't survive a tab close i'm not opposed to making the latter an option though

> memory wouldn't survive a page refresh That isn't very common. > sessionStorage wouldn't survive a tab close When a tab is restored, the browser typically restores sessionStorage. > i'm not opposed to making the latter an option though That isn't what I was getting at. If I'm going to buy into htmx, I want to understand the design. I wondered why this was the default, and why I hadn't seen it mentioned as a securit…

Maybe because I'm "old" and use browsers the way they were used when I first started using the Internet, but I refresh often enough that I'd quickly lose patience with an "app" that broke because I used a very basic feature of the web.

Re: Htmx 2.0.4 Released

#29

Earlier quoted context omitted.

> memory wouldn't survive a page refresh That isn't very common. > sessionStorage wouldn't survive a tab close When a tab is restored, the browser typically restores sessionStorage. > i'm not opposed to making the latter an option though That isn't what I was getting at. If I'm going to buy into htmx, I want to understand the design. I wondered why this was the default, and why I hadn't seen it mentioned as a securit…

Maybe because I'm "old" and use browsers the way they were used when I first started using the Internet, but I refresh often enough that I'd quickly lose patience with an "app" that broke because I used a very basic feature of the web.

If the site wasn't working it wouldn't break, it would download each page when you hit the back button. That would actually be a welcome result if I hit the refresh button wanting to make sure I was only looking at fresh data.
Post reply on HN