: and that's not about Polymer, it's about how Polymer is using selective Custom Elements ugprade
-
-
Replying to @slightlylate
isn’t PWA/ServiceWorker supposed to work equally well for all FWs according to
@addyosmani? Now it’s WC specific?1 reply 0 retweets 1 like -
Replying to @youyuxi
: no, of course it's not FW specific. It's just that Polymer has done the best job to date of wrapping it all up.
1 reply 0 retweets 1 like -
Replying to @slightlylate @youyuxi
: I'm confident that Vue.js can adopt a lot of these techniques and get much faster as a result.
2 replies 0 retweets 2 likes -
Replying to @slightlylate @youyuxi
: the thing to be watching for here is "time to interactive".
1 reply 0 retweets 3 likes -
Replying to @slightlylate @youyuxi
I want to see as *many* devs empowered to ship fast PWAs as possible. We'll get out more tooling & guides on TTI soon
1 reply 2 retweets 7 likes -
Replying to @addyosmani @slightlylate
I like the way PWA is being pushed way better than WC - i.e. showing how a concept works with existing FWs
1 reply 0 retweets 5 likes -
focusing on how to adapt rather than how you have to throw away your old junk for the future
3 replies 0 retweets 7 likes -
Replying to @youyuxi
: PWAs are mostly additive tech, not solutions to deep problems with existing frameworks.
2 replies 0 retweets 3 likes -
Replying to @slightlylate @youyuxi
: and yes, I'm calling out problems with cultural JS as practiced at scale today. Don't expect FW authors to like that
2 replies 0 retweets 4 likes
: but that's fine. Users are hurting. We need to do better. Now, let's talk about *how*
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.