#UseThePlatform doesn't mean "no" to JS, but "yes" to powerful HTML and CSS features. Don't build for JavaScript, build for the Web!
-
-
Replying to @justinfagnani
sounds ok but let's not talk down to the millions of developers who have built the web we have today.
2 replies 3 retweets 14 likes -
Replying to @wycats @justinfagnani
I thought
@addyosmani hit the nail on the head. Don't message a sharp break, message evolution. More realistic.1 reply 1 retweet 12 likes -
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 -
Replying to @wycats
Sorry, "locked in" is simply the truth of today. Projects have a hard upfront decision to make about frameworks because of it.
1 reply 0 retweets 0 likes
that will likely be true forever. The platform is not going to bake in whole app architecture and that matters a lot.
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.