but 1. that’s not the intention of FW authors; 2. FWs are still a net improvement vs. old platform sans new primitives
-
-
Replying to @youyuxi
: right. What I'm getting at is that frameworks can create "overhang". Major un-banked opportunities to go faster.
2 replies 0 retweets 0 likes -
Replying to @slightlylate
that is true, but the overly negative narratives against FWs feel like placing all the blames on FW authors
1 reply 0 retweets 1 like -
Replying to @youyuxi
: FW authors are in a privileged position. Default FW choices become the most-common outcomes for apps that adopt them.
2 replies 0 retweets 0 likes -
Replying to @slightlylate
but on the other hand FW authors also can play the critical role in accelerating adoption of new primitives, if done right
1 reply 0 retweets 1 like -
Replying to @youyuxi
: ...which is exactly why frameworks like Polymer exist. To show what's possible and help accelerate adoption.
2 replies 0 retweets 1 like -
Replying to @slightlylate
but bashing other FWs in the meanwhile? Is that necessary?
1 reply 0 retweets 5 likes -
-
Replying to @slightlylate
: if anything, folks get grumpy at me for being *vague*.
2 replies 0 retweets 1 like -
Replying to @slightlylate
: and if you acknowledge that this is a market, then markets need pricing functions. Today, that's been shit that doesn't matter.
1 reply 0 retweets 1 like
: e.g., DBMon perf isn't the bottleneck for basically any mobile site. Never was.
-
-
Replying to @slightlylate
: so saying "you should price frameworks differently" might *sound* like "bashing", but it's really just reevaluation.
1 reply 0 retweets 2 likes -
Replying to @slightlylate
: and that's not going to be comfortable for anyone.
1 reply 0 retweets 0 likes - 16 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.