so work scheduler falls back to good old list.map(func) if component already built.
so we have responsive loads and fast updates.
probably passing in some sort of node object into the state (under _node ?) so work scheduler can check this, (alreadyPrinted or whatever)
also see if there is any way to speed up updates on a large component, such as by only mapping / iterating those rows / cells, where the state they reference (state attr, state key, state object) has actually changed.
so work scheduler falls back to good old list.map(func) if component already built.
so we have responsive loads and fast updates.
probably passing in some sort of node object into the state (under _node ?) so work scheduler can check this, (alreadyPrinted or whatever)