Re: [WICG/webcomponents] [DOM Parts] Add new declarative syntax and update iterative proposal (PR #1023)

**If you agree, please downvote this proposal.**

By imposing extra curly brace in attributes you are:
* adding extra 2 characters with no advantage behind
* increasing the reading complexity
* introducing additional syntax/parser into platform where enough parsers already exist
*  adding more diversity to syntax where existing ones can be reused

From prospective of normal developer and manager `{{ }}` is additional cost for training and skills.
I do not see any positive features related to such syntax. But there are bunch of draw backs. 


What is available on the platform as of now?
* JS template syntax. `${jsExpr}`. At least all who do the web development familiar with this syntax and parser is part of JS engine. The question of JS scope vs template context recognition is not related to template syntax, and in current state of things is allover industry where JS context been part of templates. Say in JSX. Not template-oriented though. Useful mostly in embedded context.
* XSLT/XPath syntax. `{xPathExpr}` is a shorter and still quite powerful. My favorite due to template-oriented features. 

Both syntax are available for DX as
* evaluation `eval()` and API accordingly
* well tested, time proven
* have a tons of validators as in CLI as in IDE level
* syntax colored

And all of this usefulness you want to dump in favor of custom solution?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/pull/1023#issuecomment-1661386280
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/pull/1023/c1661386280@github.com>