Re: [w3c/webcomponents] HTML, CSS, and JSON modules shouldn't solely rely on MIME type to change parsing behavior (#839)

> it's the most direct expression of intent...
> Practically I see executable permission being orthogonal to formats. 
> Don't get me wrong, I'm totally open to solving the multiple representations problem. What I'm missing is the desire to lump the "can execute" problem together with it.

I think this was covered upthread, but is TC39 dead set against the possibility of a new keyword?  I agree that "noexecute" is the most direct expression of intent, but another way of looking at the problem is that we're overloading the meaning of `import` in the first place, to mean either "execute this script and give me one or more of its exports" or "parse this static, external content and give me an object representation of it".  Was it a mistake to use one word for both meanings in the first place?  Is it too late to consider an alternative?

In keeping with the Two Hard Problems, I'm hesitant to suggest a keyword name for the load-non-script-file operator.  All my off-the-cuff ideas are pretty terrible, like `get` or `import const`.  The best  I could come up with was a static-keyword version of `fetch` that would make `fetch` vs `fetch()` work like `import` vs `import()`, but I doubt that's possible.

-- 
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/839#issuecomment-551078313