- From: Domenic Denicola <domenic@domenicdenicola.com>
- Date: Sat, 7 Dec 2013 21:13:13 +0000
- To: Ryosuke Niwa <rniwa@apple.com>, Erik Arvidsson <arv@chromium.org>
- CC: Maciej Stachowiak <mjs@apple.com>, Elliott Sprehn <esprehn@chromium.org>, Webapps WG <public-webapps@w3.org>
From: Ryosuke Niwa [mailto:rniwa@apple.com] > Also, I'd like to hear opinions and perspectives of people who are not affiliated with either Apple or Google since the discussion is not going anywhere between us. In that case, web developer here. I feel that keeping them separate is much nicer. Separating these concerns seems obvious, and I am surprised anyone is trying to mash them together into one API. Higher-level utility libraries can be built in user-space, and if one is clearly a beautiful flower that everyone loves, then we can standardize that later. I definitely don't think the proposed extension is anywhere near that level. It's a confusing extra parameter that ties together the previously-unrelated concepts of shadow DOM, templates, and custom elements, not a jQuery-esque layer of sugar that makes developers lives easier. In other words, this extra parameter is an ugly and confusing piece on top of the base primitives. Wait for someone to create a useful unifying library, then standardize *that*. Don't make stabs in the dark at ways to unify these specs via ad-hoc shortcuts grafted onto the base-level primitives.
Received on Saturday, 7 December 2013 21:13:44 UTC