3 ms·
No, the entire point of borrowing the term transitional is "having the best of both worlds". The SPA/MPA comparison is about highlighting the best aspects of ea
by seumars 5y ago
No, the entire point of borrowing the term transitional is "having the best of both worlds". The SPA/MPA comparison is about highlighting the best aspects of each method and envision ways of implementing both. Any decent framework nowadays can be used to implement "transitional" features, so HTMX using this as a way to plug their own is lazy and annoyingly counterproductive in this particular discussion.
- recursivedoubts 5y agowe were asked multiple times for a response to Mr. Harris' talk, and so we gave one i think you are missing the hypermedia vs. RPC aspect of the discussion, and the javascript-everywhere vs. Hypermedia-On-Whatever-you'd-Like aspect of it, which i believe are relatively unique in the discussions i have seen but, it is fair, both laziness and self-promotion are forever a danger for me
- seumars 5y agoI get the argument, though I wouldn’t call it unique given how long JS fatigue has been a thing. HTMX is just one piece of the puzzle though so a more correct comparison would be a mature application built with htmx vs say sveltekit, not a list of cherry picked htmx features.
- recursivedoubts 5y agoI reiterate, I was responding to Mr. Harris' presentation, and showing how a hypermedia approach can address his specific concerns with MPA applications. There are other more comprehensive and philosophical articles (as well as podcasts, etc.) available on the talk page. A sibling comment offers a perhaps useful comparison: https://news.ycombinator.com/item?id=29695531 https://news.ycombinator.com/item?id=29695531