3 ms·

I dont think it has to be all or nothing. I think the best answer is to use both technologies as appropriate even in the same app. I was writing something like

I dont think it has to be all or nothing. I think the best answer is to use both technologies as appropriate even in the same app. I was writing something like htmx without intercooler with Angular with Django (which I fondly called Djangular) in 2013. It just needed yet another framework type abstraction to reduce the boiler plate. Send json with the html on initial page load, use the json api to load addition data, hard navigate between "sections" of the app but tabs and such were SPA pattern. I think a middle ground combo of svelte and htmx is a killer idea (similar to all the "live view" stuff people are loving).

recursivedoubts 5y ago
Indeed that is what Mr. Harris calls a "transitional" app, and, with him, I can recommend that approach. The difference between us on that matter would be that I would recommend leaning hypermedia, whereas, at the risk of putting words into his mouth, he would appear to lean SPA/RPC as the default approach.
- akiselev 5y ago
  > The difference between us on that matter would be that I would recommend leaning hypermedia, whereas, at the risk of putting words into his mouth, he would appear to lean SPA/RPC as the default approach. Isn't the default essentially @svelte/kit now? That's got SSR built in and a preloading layer that's much closer in nature to HTMX than to an SPA framework. RPC just happens to be the easiest way to abstract out data for static sites, SPAs, and runtime SSR.