[nilliams]

This is rendering a component server-side though correct, a la. React?

(In the comment above Tom is suggesting fastboot goes significantly further than this, to make your 'client-side app' render server-side).

[leeoniya]

i'm not sure i understand the distinction you're making.

you write a client-side app and can render on server via Node and hydrate/attach the js on client after the dumped html. you get "instant" initial render and "progressive enhancement" once the js executes.

...or do everything on client.

[nilliams]

My naive understanding is fastboot actually understands stuff like your client-side routing, and how an Ember app 'loads' and fetches data (from your API) so you don't have to recreate that stuff with duplicate code on the server-side like you would have to with the aforementioned React example, and I think, your library.

[leeoniya]

i think it heavily depends on how coupled your router is to your view and data/fetch layer. with domvm everything is decoupled, so wiring any of those modules up is pretty trivial.

a more fleshed-out demo would be valuable for a more realistic comparison. they mention the non-congruence between ajax vs node's fetch, but this is easy to shim so the same code works on both.

the main complexity is the view rendering and post-render hydration.