* Ryosuke Niwa wrote:
>Yeah, template element will be super useful for my use case though it
>doesn't address all edge cases because I have to tweak the DOM depending on
>the dataset I get.
Sure, from there on you go to either inventing some template language
extensions to deal with most of the use cases for that, or just allow
to embed "native" code directly, while the more static use cases will
look for proper direct data binding so you just have to update on the
data layer and the presentation layer will update automatically, and
so on and so forth really, nothing new here, many communities did go
through this process already.
Personally, my use cases would mostly revolve around "make stuff that
works", meaning I would not use Element.create because at first it'll
break in old browsers and be buggy in new browsers, and in the longer
run it will poorly integrate with the libraries I am using to avoid
the perpetual "inconsistent support, bugs everywhere" problem, or the
"JavaScript is a horrible language" problem. But victims of too much
browser core radiation find this a crowd-pleaser, so what do I know.
--
BjÃ¶rn HÃ¶hrmann Â· mailto:bjoern@hoehrmann.de Â· http://bjoern.hoehrmann.de
Am Badedeich 7 Â· Telefon: +49(0)160/4415681 Â· http://www.bjoernsworld.de
25899 DagebÃ¼ll Â· PGP Pub. KeyID: 0xA4357E78 Â· http://www.websitedev.de/