Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)

> This is not a simple self contained example

True, this is a user-driven feature description. But because you are so passionate about abstracting needs from tech, we should leverage another tool that separates need from technology even more so than a utilization-centric use-case: User Stories.

Here are 3 critical User Stories for this spec issue:

1. "As a dev-user, I want to create components that leverage native element capabilities and UI in as few steps as possible."

2. "As a dev-user, I want to work with code that is easy to visualize and reason about across declarative and imperative contexts, even if I didn't write it."

3. "As a dev-user, I want to ensure the code I write is easily understood by external parties that consume and rely on my code, such as crawlers, partner apps, and other entities."

These are empirical statements of need that should drive the discussion. Solutions should be graded in large part, on their ability to optimize for these needs.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/509#issuecomment-280937087