[max_]

I was recommending htmx to some of my friends and they asked me "What does it add?"

I told them that it's value proposition was not that it "added" anything but that it "eliminated" things, like build systems, configs, and the need to use js frameworks in incidences where it's an overkill (which in my experience is majority of the cases)

HTMX is a good example/manifestation of Nassim Taleb's "Via Negative" heuristic i.e some systems can improved simply by the removal of components that are dangerous, ineffective or cause friction. As opposed to trying to improve systems by trying to add components that we think will make a system better. [0]

A lot of technology is focused on improvement by adding, but I think we should start thinking more in this paradigm of improvement by subtracting — subtraction complexity that makes systems more difficult to maintain & build upon.

[0]: https://coffeeandjunk.com/via-negativa/

[jmull]

Well... there still has to be a reason to use htmx, or else why not cut it too?

[xctr94]

Needlessly snarky… it adds a lot of value if you want to enhance HTML with dynamic behaviors that would be cumbersome to write in plain JavaScript.

[dventimi]

Go ahead. Cut out htmx as well if you don't need incremental updates without having to write JavaScript.

[dunk010]

Reminds me of this: https://programmingisterrible.com/post/139222674273/write-co...

“Write code that is easy to delete, not easy to extend.”

[yawaramin]

“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.”

― Antoine de Saint-Exupéry

[cdcarter]

"do more and more with less and less until eventually you can do everything with nothing" - R Buckminster Fuller