4 ms·
I know this is a joke post, but there's some happy middle ground that's possible too, without going full SPA. If you render your pages and snippets on the serv
by cschneid 10y ago
I know this is a joke post, but there's some happy middle ground that's possible too, without going full SPA.
If you render your pages and snippets on the server, a small amount of JS on the client can hotswap content. In the extreme of this idea, you get turbolinks from Rails where no real pageloads happen, but pages are rendered on the server.
But in the small, it can let you do a sprinkling of async calls where they make the most sense, and still keep all rendering of responses on the server.
Thoughtbot wrote about it recently:
https://robots.thoughtbot.com/how-we-replaced-react-with-phoenix https://robots.thoughtbot.com/how-we-replaced-react-with-pho...