>
andybak 7 hours ago | parent | on: Intercooler.js – Making AJAX as easy as anchor tag...
> You have the API inflexibility and UX restrictions of a pure-HTML approach
I don't see this. Can you elaborate?
No client-side rendering. More precisely, the core idea of intercooler is that every UI update polls the server for new markup. So for each non-trivial UI change, you have to take into account the latency of a network request, even if you already sent the data to the client before in another request. That makes the "feels like a desktop app" experience impossible that originally was one of the major selling points of ajax.
The "markup snippet" means that if you want to change your UI, congratulations, you have to change your template and your API - whereas with client-side rendering you wouldn't have to touch the API at all in many cases.
> In what sense? Bandwidth? Rendering? Conceptual?
Conceptual. You have the same complexity costs as a full ajax page compared to a plain-html page (data gathering spread over multiple requests, need to define an API boundary, need to care about clients without JS support, need to track client-side state, etc.) - but it seems to me you get a lot less benefits for that cost.
> It is a small evolution of on from pjax/turbolinks - which itself epitomises progressive enhancement/graceful degradation.
I admit I'm not familiar with that. But how would it deal with clients without JS support?