How do desktop-era JS frameworks stay competitive on the mobile web? My JSConf EU/DinosaurJS talk, now in blog form!https://tomdale.net/2017/04/making-the-jump/ …
-
-
Replying to @tomdale
My biggest regret about this talk is I didn't find a way to talk about webpack.
3 replies 0 retweets 5 likes -
Replying to @tomdale
Webpack has had the single biggest practical impact in reducing the cost of code for JavaScript apps, by a wide margin.
3 replies 4 retweets 26 likes -
Replying to @tomdale
Route-based code splitting just fundamentally changes the equation of how small you can make "SPAs" without damaging developer productivity.
2 replies 1 retweet 22 likes -
Replying to @tomdale
Yeah, one of the things I'm most looking forward with ng2.
@slightlylate et al don't talk enough about it1 reply 0 retweets 0 likes -
I don't? It's basically what I drone on and on about when allowed and why I'm such a fan of things that bake this is *by default*.
2 replies 0 retweets 2 likes -
Replying to @slightlylate @tomdale
Keyword "route based" is the key. Routes are an easy splitting cutoff point in current fw's. Higher granularity gets real hard
1 reply 0 retweets 0 likes -
This (and lower framework overhead) are why I've been banging the Polymer App Toolbox drum...so I guess mission accomplished?
1 reply 0 retweets 0 likes -
Replying to @slightlylate @tomdale
That involves polymer and... (you know the rest)
1 reply 0 retweets 0 likes
Great! Go catch up to them in whatever way gives you warm fuzzy feelings....just *please* catch up.
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.