Conflating a unit of code organization (ES6 module) with a unit of code delivery (HTML import) is a mistake.https://twitter.com/slightlylate/status/792014657506516992 …
-
-
Replying to @cramforce
I don’t have particular opinions about HTML imports, but giving Es6 modules a role in code delivery is dangerous.
3 replies 0 retweets 1 like -
Replying to @cramforce
: I'm not sure that's true. <script type="module"> is good stuff. But it's not enough.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
I don’t see a path to HTTP-request-per-module being efficient any time soon.
2 replies 0 retweets 1 like -
Replying to @cramforce
: a few (belated, travel) things: 1. <script type="module"> is essential for delivery as it enables xform into inline Imports
1 reply 0 retweets 2 likes -
Replying to @slightlylate
2. The biggest issue for mobile perf is how much we load. Major advantage of Imports + route based loading is minimisation
1 reply 0 retweets 2 likes -
Replying to @slightlylate
3. Best thing about Imports in smaller projects (~Shop-sized) is that you don't have to contort resources for deploy.
2 replies 0 retweets 0 likes
What I'm seeing here is tools taking people too far away from the costs of their decisions. Directness of action is a virtue.
-
-
Replying to @slightlylate
*checks thread to see if you're talking about the Touch Bar or the web*
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.