Skip to content

nested e/for-by introduces needless latency #53

Description

@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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions