:::note This post describes a renderer that has been deleted
Everything below is written about the ExoNodeDom three-props runtime — h(type, attrs), static / bindables / bindableLists, defineComponent, and the
@exodra/babel-plugin-jsx compiler. None of that exists any more. @exodra/core
states the deletion in its own barrel (packages/core/src/index.ts:10-12), as does
@exodra/dom (packages/dom/src/index.ts:9-10), and the babel plugin has been
replaced by @exodra/babel-plugin-schema. Do not write code from this post, and do
not hand it to an assistant as a description of Exodra.
What survived is the argument, not the API. A component is now one value
carrying two halves — a schema built once at module load, and a wiring function
run per instance (exoComponent(build, P => wire)). The schema declares ports;
the wiring fills them with a verb that says how: c.set once, c.bind kept in
step, c.on a listener, c.bindList a reconciled children port. The bucket is gone;
"the renderer never has to ask what kind of value this is" is exactly why. See
Core Concepts and Getting Started.
It is kept because a post is a record of what was believed when it was written.
:::
Every reactive framework faces the same dilemma: how to handle different types of properties efficiently. Most frameworks choose developer convenience over performance. We chose performance.