3 ms·

I prefer to refer to htmx as a "future polyfill". Eventually, htmx semantics will become part of the web standard, and older browsers (or those that choose not

I prefer to refer to htmx as a "future polyfill". Eventually, htmx semantics will become part of the web standard, and older browsers (or those that choose not to implement the feature) will need this polyfill.

hobofan 3y ago
> Eventually, htmx semantics will become part of the web standard Why do you think that will be the case? I'm not aware of any effort being made to evolve htmx into a web standard (either by introduction into existing specifications or direct adoption by browser), so this is about as baseless of a claim as someone saying "I see JQuery as a future polyfill" in ~2006.
- intrasight 3y ago
  s/will/may It may be aspirational on my part, but I do hope that HTML can evolve. JQuery isn't a good analogy as it's not extending HTML.
- jbverschoor 3y ago
  Because it's a damn good name. As a matter of fact, when I read about HTMLX, I assumed it was a browser supported feature that I had missed
  - intrasight 3y ago
    Hadn't considered it before, but thinking about it now, I can see that a brilliant name choice probably played a big role in the traction that it's had.
    - recursivedoubts 3y ago
      ironically I originally rejected it in favor of "kutty": https://htmx.org/posts/2020-5-17-kutty-er-htmx-0-0-3-is-released/ https://htmx.org/posts/2020-5-17-kutty-er-htmx-0-0-3-is-rele... better to be lucky than good, I guess
      - intrasight 3y ago
        I, for one, am glad that you didn't release a self-harm framework ;)
        recursivedoubts 3y ago
        yeah, looking back it's ridiculous, how could I not use htmx when I had managed to snag htmx.org? but I'm an idiot. thankfully the fates conspired to force my hand
  - twic 3y ago
    The X is a bit meaningless though. Xtended? It could have leaned into the hypermedia angle and been Hyper-HTML, or H2ML.
moritzwarhier 3y ago
CoffeeScript inspired ES2015, jQuery inspired querySelector and some other DOM APIs, but none of them would be a usable polyfill, and the standard APIs/syntax is not the same. Apart from that, I'm not sure if I even agree with the point as a metaphor. Some parts of htmx would make it easier to implement a form submit confirmation message or similar stuff. everything else is either better served fully server-side or needs heavier client JS. E.g. ajax pagination is useless without routing... well maybe I need to try htmx more thorougly to understand this stance. right now I don't. it's not hard to do a fetch request and set innerHTML on an element, right?

hobofan 3y ago

> Eventually, htmx semantics will become part of the web standard Why do you think that will be the case? I'm not aware of any effort being made to evolve htmx into a web standard (either by introduction into existing specifications or direct adoption by browser), so this is about as baseless of a claim as someone saying "I see JQuery as a future polyfill" in ~2006.

intrasight 3y ago
s/will/may It may be aspirational on my part, but I do hope that HTML can evolve. JQuery isn't a good analogy as it's not extending HTML.
jbverschoor 3y ago
Because it's a damn good name. As a matter of fact, when I read about HTMLX, I assumed it was a browser supported feature that I had missed
- intrasight 3y ago
  Hadn't considered it before, but thinking about it now, I can see that a brilliant name choice probably played a big role in the traction that it's had.
  - recursivedoubts 3y ago
    ironically I originally rejected it in favor of "kutty": https://htmx.org/posts/2020-5-17-kutty-er-htmx-0-0-3-is-released/ https://htmx.org/posts/2020-5-17-kutty-er-htmx-0-0-3-is-rele... better to be lucky than good, I guess
    - intrasight 3y ago
      I, for one, am glad that you didn't release a self-harm framework ;)
      - recursivedoubts 3y ago
        yeah, looking back it's ridiculous, how could I not use htmx when I had managed to snag htmx.org? but I'm an idiot. thankfully the fates conspired to force my hand
- twic 3y ago
  The X is a bit meaningless though. Xtended? It could have leaned into the hypermedia angle and been Hyper-HTML, or H2ML.

moritzwarhier 3y ago

CoffeeScript inspired ES2015, jQuery inspired querySelector and some other DOM APIs, but none of them would be a usable polyfill, and the standard APIs/syntax is not the same. Apart from that, I'm not sure if I even agree with the point as a metaphor. Some parts of htmx would make it easier to implement a form submit confirmation message or similar stuff. everything else is either better served fully server-side or needs heavier client JS. E.g. ajax pagination is useless without routing... well maybe I need to try htmx more thorougly to understand this stance. right now I don't. it's not hard to do a fetch request and set innerHTML on an element, right?