nested e/for-by introduces needless latency

[dustingetz]

If you nest your e/for-bys too deeply you start to notice the page loading in "stratas" where each layer of e/for-by must complete before the next layer finishes. The root of the problem is that the e/for-by is wholly contained by one peer, not split, which is undesirable and constrains expressive power. However, this is not noticed by most users unless working with 3-4 levels of nesting (e.g. tree forms)

Can be resolved after after Differential Electric lands, under which the Electric runtime is aware of collections and diffing, so that the network planner has access to knowledge about e/for nesting depth which is needed to plan the network correctly here.

[avocade]

Please do tell more about this Differential Electric , sounds cool.