html-json-size-comparison

I find this no-nonsense approach very appealing. > The more you render from the server, the larger your caches end up. Not doing that for HTML. Is HTML really that much larger or complex than JSON? Based on the following it seems to be only +10-15% larger (n = 1 dataset obviously). https://github.com/1cg/html-json-size-comparison Is the amount of data transfer the main reason to use JSON or do you find Web Components play better with JSON payloads? I could imagine the template string being rendered on the server, fetch()-ed by the client and swapped with this.innerHTML. Do you manage any amount of cross-component state? It's one use case where JSON would win over "HTML over the wire".

Yeah, that was too short a response, sorry I was bouncing around a lot in the thread. The essay I linked to somewhat agrees w/your general point, which is that hypermedia is (mostly) wasted on automated consumers of REST (in the original sense) APIs. I don't think it's a bad thing to split your hypermedia API and your JSON API: https://htmx.org/essays/splitting-your-apis/ (NB, some people recommend even splitting your JSON-for-app & JSON-for-integration APIs: https://max.engineer/server-informed-ui) I also don't think it's hard to avoid duplicating your effort, assuming you have a decent model layer: https://htmx.org/essays/mvc/ As far as efficiency goes, HTML is typically within spitting distance of JSON particularly if you have compression enabled: https://github.com/1cg/html-json-size-comparison And is also may be more efficient to gen

ceteris is rarely paribus: JSON-based APIs have to make a choice between being general purpose, in which case a web app written against them may end up chatty with multiple requests per page, or they end up application specific, in which case they can be churney and a bad general purpose API. I wrote an essay about this here: https://htmx.org/essays/splitting-your-apis/ Also, producing JSON often involves reflection and can be more CPU intensive than straight templating (w/ fixed properly lookups) depending on your technology. Finally, the size delta between JSON and hypermedia is lower than most people think, particularly with compression: https://github.com/1cg/html-json-size-comparison in most real world systems i expect data store access to be the dominant latency issue some people have had good success w/htmx from a performance pers

See for yourself: https://github.com/1cg/html-json-size-comparison

htmx does not require you to make a server request for every interaction: https://hypermedia.systems/client-side-scripting/ i would note that if you are going to make a server side request, HTML can be faster than the equivalent JSON: https://github.com/1cg/html-json-speed-comparison https://github.com/1cg/html-json-size-comparison