- From: Sasha Firsov <notifications@github.com>
- Date: Sat, 27 Aug 2022 23:38:24 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <WICG/webcomponents/issues/704/1229391809@github.com>
The question of long-term vision and high level goals is not something folks are not thinking those days. The sad side not in WICG forum which meant to be incubator for innovations. WCCG is asking for [Where do you see yourself in 5 years? ](https://github.com/w3c/webcomponents-cg/discussions/39), I am collecting thoughts myself [1](https://github.com/EPA-WG/EPA-concept/issues/5), [2](https://github.com/EPA-WG/EPA-concept/issues/6), but still looking into proper forum to discuss the high-level goals and creation of non-conflicting concepts and implementations. Aforementioned is just a sample how some folks see the vision as important part of current decision making. Would be nice to see such vision fit here, in templates implementation discussion. My take: templates are essential part of web application development SDLC. Which includes modularity, concept of libraries with own scope, ability to load as a bulk, caching across page loads, etc. In the ongoing web app stack templates are essential part of declarative custom elements; IMO outdated concept of declarative shadow DOM. The parts compete with slots and meant to be just a syntax sugar over what slots meant to support out of the box( needs ATTRIBUTE and PART be exposed as HTML tags ). In order to have a clear picture the concepts above at least meant to be discussed as a whole. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/704#issuecomment-1229391809 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/704/1229391809@github.com>
Received on Sunday, 28 August 2022 06:38:37 UTC