undefined | Better HN

0 pointsdaliwali8y ago0 comments

Using class names was just an example, people may get the wrong impression that has anything to do with the variable name. It could have been made more explicit, but I wanted to be as terse as possible:

    <h1 class="name" data-bind="name"></h1>

It was also a design goal not to introduce a templating syntax, so `{{}}` brackets are out of the question.

0 comments

TekMol8y ago

I see now, that the bindObject() function takes a mapper from data to DOM.

There are two downsides to this:

1) You have to define twice where the data is displayed. Once in the template and then again in the mapper.

2) <div>{{NAME}}</div> explicitly tells the reader "The name goes here". In your solution one would have to look it up in the mapper to be sure what goes where.

daliwaliOP8y ago

I'm well aware that there must be an element and a selector for that element. But this is exactly how CSS works as well, it's separation of concerns. Only recently have inline styles become trendy, much to my dismay.

The total absence of templating syntax is a deliberate decision. It enables one to start from an HTML mock-up or static page, and build interactivity on top of that without changing any HTML.

TekMol8y ago

    this is exactly how CSS works as well

I beg to differ. There is no mapping needed for CSS. CSS works by once defining where the style shall go:

    <div class=city></div>

And once what the style is:

    .city {color: blue; font-family: arial;}

Similar, template syntax once defines where the data shall go:

    <div class=city>{{NAME}} has {{POPULATION}} residents</div>

And once, what the data is:

    city={name: "New York", population: 8491000}

Neither need additional mapping.

1 more reply

j / k navigate · click thread line to collapse

0 comments

TekMol8y ago

I see now, that the bindObject() function takes a mapper from data to DOM.

There are two downsides to this:

1) You have to define twice where the data is displayed. Once in the template and then again in the mapper.

2) <div>{{NAME}}</div> explicitly tells the reader "The name goes here". In your solution one would have to look it up in the mapper to be sure what goes where.

daliwaliOP8y ago

The total absence of templating syntax is a deliberate decision. It enables one to start from an HTML mock-up or static page, and build interactivity on top of that without changing any HTML.

TekMol8y ago

    this is exactly how CSS works as well

I beg to differ. There is no mapping needed for CSS. CSS works by once defining where the style shall go:

    <div class=city></div>

And once what the style is:

    .city {color: blue; font-family: arial;}

Similar, template syntax once defines where the data shall go:

    <div class=city>{{NAME}} has {{POPULATION}} residents</div>

And once, what the data is:

    city={name: "New York", population: 8491000}

Neither need additional mapping.

1 more reply

j / k navigate · click thread line to collapse