Re: [webcomponents] How the current model and the v1 model should interact? (#130)

It's a tradeoff that we need to think through carefully. I think the decision depends on balancing

1. the number of developers who will encounter the problem you described above
2. the cost of implementation complexity

To understand the number in the first item, we could the component v0/component v1 scenario into 2 buckets:

1. Both v0 and v1 are made using the same framework that doesn't support multiple versions of itself
2. v0 and v1 are made using the same framework that supports multiple versions of itself or using different frameworks or custom-made

The bucket 1 is all good, because then it is the framework's responsibility to homogenize (or disallow) v0/v1 components across. The bucket 2 is highly problematic, because then the burden of encountering and resolving breakage falls on the user of the component (not the developer).

So.. the questions are: how big is bucket 2 and how does it compare with the cost of complexity?


---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/130#issuecomment-140140956