I thought @addyosmani hit the nail on the head. Don't message a sharp break, message evolution. More realistic.
-
-
Replying to @wycats
's talk is great for those already bought into large JS-heavy systems, showing you can still benefit from the platform
1 reply 0 retweets 0 likes -
Replying to @justinfagnani @wycats
I don't think
@addyosmani would disagree with#UseThePlatform to make simpler, lighter-weight, faster, less locked-in systems.2 replies 0 retweets 0 likes -
Replying to @justinfagnani @addyosmani
this message is really corrosive and creating antagonism between allies.
2 replies 1 retweet 20 likes -
Chrome's job is to improve the platform. Our job is to bring those innovations to as many ppl as possible.
1 reply 1 retweet 15 likes -
"locked in" "large JS-heavy" reflects marketing for a framework not platform improvements.
2 replies 0 retweets 15 likes -
we all have work to do and we're on the same side. Let's act like it.
2 replies 0 retweets 28 likes -
I think the key is setting the bar and then frameworks cam compete on dx etc
1 reply 0 retweets 4 likes -
works for me. An actual target to hit sounds awesome.
#TooMuchJS is not a performance metric.2 replies 0 retweets 5 likes -
But it's not untrue either. We shouldn't shy away from advice because it's not a specific #
1 reply 0 retweets 1 like
it's actually wrong. It doesn't have anything to do with timing at all.
-
-
Replying to @wycats @justinfagnani and
"too much synchronous JS all at once before interactivity" is real.
2 replies 0 retweets 0 likes -
Replying to @wycats @justinfagnani and
but if you say that people will notice that there's something to do other than delete your framework.
0 replies 0 retweets 0 likes
End of conversation
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.