On Apr 13, 2013 8:08 PM, "Bjoern Hoehrmann" <derhoermi@gmx.net> wrote: > > * Sylvain Galineau wrote: > >On 4/13/13 3:57 PM, "Bjoern Hoehrmann" <derhoermi@gmx.net> wrote: > >>* fantasai wrote: > >>>So, at Rename the Web Forward [1], Sylvain and I concluded that it > >>>just might be better to use 'set-' as the prefix and 'get()' as the > >>>function name instead of 'var-' and 'var()'. > > >>Well, `get` and `set` as used here are imperative, while CSS tries to be > >>a declarative language, so this seems rather confusing to me. > > >What, specifically, would an end-user be confused about and how would this > >confusion manifest itself? > > The `var-` prefix exists only because a namespacing mechanism is needed > to avoid clashes between pre-defined and author-defined properties. The > `set-` prefix conveys that even less than `var-`. We call `color: blue` > a declaration, but `set` does not "declare", it "sets"; obviously there > would be a reason why the designers of this syntax chose "set" as name, > rather than something with more declarative semantics, so custom proper- > ties work differently than normal properties. Obviously `get` would get > the value associated with the name when it was last `set`, and "when" is > temporal, so in order to understand what value `get` retrieves, I have > to understand the execution order of the `set` instructions... > -- As opposed to understanding the that var- sets and var() gets with the exact same need to understand everything else you just described, which is all normal css?
Received on Sunday, 14 April 2013 00:37:24 UTC