A Question the DOM Cannot Answer
A renderer that fills ports has two ways to spell a write.
Resolve on every write. The port carries an index, the plan carries a table of setters and a table of node slots, and each write walks both:
setters[index](nodes[elem[index]], value)
Resolve once and keep the answer. Hand out a closure that has already done the lookups, so the write is a call:
const write = setters[index];
const at = nodes[elem[index]];
return (value) => { write(at, value); };
The second looks obviously better — the lookup's answer cannot change for the life of the instance, so paying for it repeatedly looks like waste. That reasoning is why a renderer grows a second write path in the first place.
We measured it on the DOM. The measurement refuses to answer, and the refusal is the result.
