Angular hydration explained

In this video, we explore Angular hydration, a powerful technique for improving Angular application performance and user experience.

[chaos_monster]

I liked the idea of using the 3 second delay resolver to better illustrate the difference of hydration vs not. Because often with simple examples it's hard to even "see: the repaint on a local machine, because everything is so fast

[aram]

I enjoyed this video! Actually, I wouldn't mind a whole series on SSR and considerations around it, ways of testing during dev time, etc. This is a very underrepresented topic.

[AlainBoudard]

Awesome demo Kevin ! Thanks for sharing 😎

[orzohar]

cool! would you recommend to use SSR on changing table? I have a big data table that being change on every click, would you SSR it every time to reduce it's loading time?

[sasagasparovic]

I am not sure that I understand. Hydration is preventing resolvers to do on both side? Just on server in case of ssr?

[mktrann]

Hi Kevin, which VSCode icon extension you are using?

[khanhhoang]

Hi Kevin, great explanation, but I still have a confusion, SSR is for improving the performance of web applications by delivering fully rendered HTML to the client. But if Angular destroys pre-rendered HTML it does not make sense anymore

[o_glethorpe]

Everything that moves something that could be solved in the client to the server is a mistake. Users will need to wait that 3 seconds anyway. Why make it more expensive to host the app when users have powerful devices in their pockets? SSR is the most backwards trend I see in years.