Does the `binding` required, or API can be updated to only use `link` and `unlink`?

Current API design has few helpers for binding in different ways, and then element has link method. So Label to data currently is:

const label = new Label({
    binding: new BindingObserverToElement()
});
label.link(data, 'text');

And for bi-directional:

const textInput = new TextInput({
    binding: new BindingTwoWay()
});
textInput.link(data, 'text');

Question:

Is this is necessary to provide classes for binding?

Proposal:

Here is example of how it could simplify for users the data binding:

For read-only data:

const label = new Label();
label.link(data, 'text', { write: false });

For bi-directional (by default):

const textInput = new TextInput();
textInput.link(data, 'text');

For write only:

const textInput = new TextInput();
textInput.link(data, 'text', { read: false });

In JSX it will be:

<TextInput link={ data, path: 'text' } />

And to link attribute read and/or write property can be provided:

<TextInput link={ data, path: 'text', read: false } />

Start by reviewing the existing binding helper classes and the element link method described in the issue. Compare their current responsibilities with the proposed read and write options, then determine the required API behavior and JSX shape. Done means the project has a decided, documented direction with corresponding implementation scope.