I mean, it's all swings and roundabouts. You're saving on JS parse time and enabling parallel loading of assets by extracting, but sacrificing CSSOM performance. An ideal solution would give us the benefits of shadow DOM without those drawbacks
This is pretty backwards. You can always plan on an always-upgraded CE world: you just build with CE the exact same way as you do regular JS-driven UI. Define, then use.
-
-
The choice is between SSR with no pop-in upon hydration, with no polyfills required (and encapsulated styles via tooling), or SSR with pop-in upon upgrade and a requirement to polyfill. It's no wonder that even those of us who are pro-platform choose the former
-
Again, that's backwards. You inline your component definitions such that they evaluate before use; voila, no upgrade!
- 8 more replies
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.