HTML event handler attributes reserve the word "event"

[olaf-k]

As explained in the playground, event has a special meaning when used as an argument of an event handler.

To avoid possible confusion/mistakes with user-declared variables, could we adopt a specific naming convention for such cases, like $event instead?

[jakub-g]

+1, in addition, IMO we should do the same to attributes and call them $attributes. Why have $init, $render, $dispose but attributes? Consistency is important.

[ymeine]

Personally I never liked the use of naming conventions to distinguish expected properties of an object from free ones. At some point, someone could want to choose a reserved name for one of its properties, and he would not be able to do so.

Why not wrapping prototype members under a property of the definition object? (like prototype, aliased proto) Then, in this particular case, since $init, $render and so on end as direct prototype members, this would make sense to put them inside this property as well, and to keep the naming convention in this case. We can't do magical things with the API, either we identify differently in the same space or we put in different spaces.