only the "install pain" but it seems PWAs will be MUCH larger for the foreseeable future and that has implications.
-
-
Replying to @rmhrisk
: I'm not following. Why? Most PWAs I see grab resources they cache from initial payload/http-cache + a bit more.
2 replies 0 retweets 0 likes -
Replying to @slightlylate @rmhrisk
: which, if you're building it the PRPL way, is often lighter than the omnibus-JS-bundle I'm seeing so much of these days
1 reply 0 retweets 1 like -
I want to like Polymer because of PRPL. JSX/react syntax/workflow seems more productive though :/
2 replies 0 retweets 1 like -
Replying to @tankredhase @rmhrisk
: professionalism demands we prefer the tools that get good results over ones that make us feel good.
2 replies 0 retweets 2 likes -
agreed. Polymer does produce better results (especially w/ slick paper elements). But ecosystem adoption..
1 reply 0 retweets 1 like -
Replying to @tankredhase @slightlylate and
.. is higher for react. Strategic factors one can't ignore IRL. Team know-how, docs, 3rd party libs...
1 reply 0 retweets 0 likes -
Replying to @tankredhase @slightlylate and
perhaps if Polymer was used more at Google. To an outsider it looks like a research project for WC :/
1 reply 0 retweets 0 likes -
Replying to @tankredhase @rmhrisk
: with pass that along to the YouTube folks who built all of YT Gaming in it. Or Music.
1 reply 0 retweets 0 likes -
great showcases, yes. FB uses react (native) in the core app --> ecosystem trust++
2 replies 0 retweets 1 like
: we, OTOH, have more than one app & those teams set their own goals/paths
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.