terminology: why @click instead of onclick etc

[MentalGear]

I appreciate the mission of building a "Web Standards Stack" framework, but I'm wondering why you are using @click instead of the standards based onclick (which svelte has also moved towards), and own attributes like @name instead of "id".

I think a standards stack framework that wants to be consistent should also use those standard terms, or at least provide a sensible explanation in the guide why it can't.

[tipiirai]

The idea is to pass the standard onclick attribute to the browser and @click is dealt by the compiler. Vue compatibility was also a thing on the original desing. However, I have started to feel that onclick is better. Similartly ${ expr } rather than { expr } for expressions to make it closer to standards. So definitely on board with your thinking. Hard to find decent alternative for @name. id specifically is troublesome because sometimes the component needs the standard id attrube and sometimes not, and repeating it is not allowed. Suggestions?

[MentalGear]

Thx for the open exchange.

Yeah, everything that's standard makes it easier to migrate to your frameworks, or makes learning it also a transferable skill.

Svelte uses this attr instead of name to identify elements, but I think name is better.

Maybe in this case it's good to keep the @ for attributes that are just used in the framework.