So we <link preload /> all the files?
-
-
-
<link rel=modulepreload> See https://developers.google.com/web/updates/2017/12/modulepreload … by
@sergiomdgomes
End of conversation
New conversation -
-
-
Why add a new attribute? Why not: <script type="module; version=2019" src="2019.mjs"> or <script type="module 2019" src="2019.mjs">
-
Makes a lot more sense (also "module/2019"). But I guess it's because of backwards compatibility with recent browsers that would not understand the new type, but at the same time would also not load the fallback with the nomodules attribute.
- 1 more reply
New conversation -
-
-
conflicted if using srcset syntax for that is the worst thing ever or the best thing ever
-
@kristoferbaxter and I disagree on this :) - 2 more replies
New conversation -
-
-
Last time I check there is no a single ES version which is fully support by any browser, so I think it's kind of problematic (and yes I wait to "Tail call optimization" in Chrome / Node)
-
Please read the proposal. None of this refers to ECMAScript version numbers. I agree that wouldn’t be useful.
- 1 more reply
New conversation -
-
-
Didn't Mozilla add versioned JavaScript tags years ago, then end up removing it?
-
The numbers do not refer to ECMAScript version numbers.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.
Should the web platform have first-class support for differential script loading?