.@phae on "Naming Progressive Web Apps"; TL;DR: opinion-havers, it's _not about you_: https://fberriman.com/2017/06/26/naming-progressive-web-apps/ …
-
-
Replying to @slightlylate @phae
@rem seems a lot like polymer and how they co opted web components. so i'm leary. what was wrong with adaptive? been around much longer.1 reply 0 retweets 0 likes -
I was there for the whole Web Components effort; Polymer didn't co-opt, it led. Revisionist history is a dangerous thing.
1 reply 1 retweet 7 likes -
and thru leading some devs never knew the difference. certainly not revisionist.
1 reply 0 retweets 0 likes -
Absolutely revisionist. If you would prefer nobody lead, you'll find yourself exactly where you started -- lots of that about, sadly.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @jalbertbowdenii and
And just so we're on the same page: I co-led the team that developed Web Components inside of Chrome and I helped hire the Polymers.
2 replies 0 retweets 2 likes -
im aware of who you are. adaptive was coined years prior to pwa. it led the way. not good enough?
2 replies 0 retweets 0 likes -
If it were, we wouldn't have needed a new name. That's the real bugger about branding: it's not about correctness, it's about the "hook".
6 replies 0 retweets 3 likes -
Replying to @slightlylate @jalbertbowdenii and
...and _that_ is about audience. "Adaptive" didn't hook with business decision makers in a way that opened doors. That's happening now.
2 replies 0 retweets 4 likes
...and yes, the coutnerfactual is fuzzy! Perhaps pushing a different boulder up the hill would have worked, but it hadn't 'till then.
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.