3 ms·

I'm a bit disappointed at the removal of SSE from core HTMX, mostly as I see SSE as being much more in-line with standard hypertext, and there does need to be s

I'm a bit disappointed at the removal of SSE from core HTMX, mostly as I see SSE as being much more in-line with standard hypertext, and there does need to be some kind of server-push-long-polling-thingy. Not very disappointed, but I do wonder why it doesn't ship with SSE as standard.

lagt_t 3y ago
IIRC it was considered scope creep.
recursivedoubts 3y ago
yeah, it was a hard decision pulling sse and web socket support out, but we've done that already in the 1.x line: the hx-ws and hx-sse attributes are deprecated in favor of extensions: https://htmx.org/docs/#websockets-and-sse https://htmx.org/docs/#websockets-and-sse our feeling was that, to do those things right would require a fair bit of code and it wasn't fair to all htmx users to make them pay that freight, as these were more advanced features that many people would not be using another feature we didn't include was idiomorph-based swapping out of the box: https://htmx.org/docs/#morphing https://htmx.org/docs/#morphing that was really hard to not include because it's a neat algorithm that i came up w/ and it's going to be included in the next version of Rails, but, again didn't feel it was fair to make everyone pay for it
- pseudosavant 3y ago
  FWIW, since it is so easy to include extensions, I think you made the right choice. That said, for the project I want to try HTMX out on, I will definitely be trying out idiomorph swapping. Sounds novel and useful.
- jemmyw 3y ago
  That's interesting, I assumed htmx already did morph the dom this way. The company I work for has a similar but custom system in place they built 10 years ago that morphs the dom for those reasons (came up in a meeting last week, it was made before I joined). Shame it wasn't open sourced back then, it's pretty neat solution with websocket signalling to do multi user screen updates.

lagt_t 3y ago

IIRC it was considered scope creep.

recursivedoubts 3y ago

yeah, it was a hard decision pulling sse and web socket support out, but we've done that already in the 1.x line: the hx-ws and hx-sse attributes are deprecated in favor of extensions: https://htmx.org/docs/#websockets-and-sse https://htmx.org/docs/#websockets-and-sse our feeling was that, to do those things right would require a fair bit of code and it wasn't fair to all htmx users to make them pay that freight, as these were more advanced features that many people would not be using another feature we didn't include was idiomorph-based swapping out of the box: https://htmx.org/docs/#morphing https://htmx.org/docs/#morphing that was really hard to not include because it's a neat algorithm that i came up w/ and it's going to be included in the next version of Rails, but, again didn't feel it was fair to make everyone pay for it

pseudosavant 3y ago
FWIW, since it is so easy to include extensions, I think you made the right choice. That said, for the project I want to try HTMX out on, I will definitely be trying out idiomorph swapping. Sounds novel and useful.
jemmyw 3y ago
That's interesting, I assumed htmx already did morph the dom this way. The company I work for has a similar but custom system in place they built 10 years ago that morphs the dom for those reasons (came up in a meeting last week, it was made before I joined). Shame it wasn't open sourced back then, it's pretty neat solution with websocket signalling to do multi user screen updates.