---
# System prepended metadata

title: 'Streamcast with Ryan: Qwik + Progressive Hydration'

---

# Streamcast with Ryan: Qwik + Progressive Hydration

## Proposed Outline

- What is Progressive Hydration
  - Why can't you just add Progressive Hydration to existing app/framework
- Let's go over each issue PH presents. (We can zoom in how Qwik solves the problem)
  - Breaking up code into multiple chunks
  - No centralized bootstrap
  - Serializing event handlers into HTML
  - Event handlers have amnesia => Restoring app state
  - Invalidating components on state change
  - Out of order rendering
    - Getting `props` from parent
    - Getting `props.chlidren` from parent (Child projection)
    - Child component references bring in too much code
    - Deciding if we should descend into children
    - Projecting children
  - Observing state change and running side-effects
  - Transient state
  - Producing ideal bundles => preventing waterfalls
  - Prefetching through web-workers
  - Good DX