While the points against hydration are valid, the proposed solution sounds to me like it would have other (opposite) performance problems: i.e. hydration has a

While the points against hydration are valid, the proposed solution sounds to me like it would have other (opposite) performance problems: i.e. hydration has an inherent startup overhead, and possibly a continuing memory overhead (though the latter doesn't seem inherent), whereas resumable sounds like it may start fast, run slow (and I can't see where they solve the mentioned memory overhead problem). I haven't tested this myself so since they have some Qwik demos linked I gave them a try. Anecdotally, startup seems very slow in them. I thought this was meant to be the problem being solved. Maybe the component download is fast but the framework download/parse is the slow part? Either way, none of the examples are complex or interactive enough to properly test ui latency so I don't know.