I'm not going to ignore the user benefit of performance. If frameworks can't hit RAIL, they're bad for users.
-
-
Replying to @jaffathecake @ryanflorence
you're assuming the conclusion. We're all working on it, and so is polymer. Nobody is "years ahead".
2 replies 0 retweets 4 likes -
this debate is really about whether FWs have to be "ditched" or "rewritten", which is really just too extreme.
2 replies 0 retweets 5 likes -
what I'd prefer is 1) acknowledgement that FWs are trying to hit RAIL, 2) positive sentiment about progress.
3 replies 0 retweets 10 likes -
addy's talk at I/O for example. more of that. less of all this ^.
2 replies 2 retweets 18 likes -
Replying to @robwormald @wycats and
What matters is giving users the fastest experience on mobile *whatever* lib/FW powers that.
3 replies 4 retweets 24 likes -
Jake Archibald Retweeted Jake Archibald
basically https://twitter.com/jaffathecake/status/770377454234038274 …, so I'm not sure why I'm still being told what I should/shouldn't say
Jake Archibald added,
2 replies 0 retweets 1 like -
Replying to @jaffathecake
+1
@wycats@ryanflorence Many Google apps need to improve perf. We know many 3rd-party ones do too. We want everyone improving3 replies 2 retweets 10 likes -
Replying to @addyosmani @jaffathecake and
from my perspective everyone is so in love with their solutions we are ignoring the problems
2 replies 0 retweets 10 likes -
Replying to @brianleroux @addyosmani and
it's kinda easy. Code spit. Lazy load. Prerender. All the fameworks *can* do this.
3 replies 1 retweet 18 likes
the key is that FWs have to find solutions that work for a wider swath of users.
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.