Re: webcomponents: <import> instead of <link>

On Wed, May 15, 2013 at 9:36 AM, Dimitri Glazkov <> wrote:
> On Tue, May 14, 2013 at 8:04 PM, Jonas Sicking <> wrote:
>> Apparently I wasn't clear enough before.
>> We shouldn't add dynamically updating imports of components just
>> because we're choosing to reuse <link>. We add dynamic imports if
>> there are use cases.
> I agree, but I am not stressed either way.
> Making imports dynamic is the least work, since we simply follow how
> <link> works in all other cases.
> Making imports non-dynamic is just a matter of a
> "have-I-ever-been-an-import" flag per <link>, and that's also quite
> easy.

I'm willing to put money on that in the long run it'll be much harder
to implement dynamic imports.

There will be much more to implementing in then what the
infrastructure in <link> will provide. There's also all sorts of data
structures where we'd need to remove the added components from, and
likely various edge cases where we'd need to put in guards.

/ Jonas

Received on Wednesday, 15 May 2013 17:57:14 UTC