Skip to content
HHackerTube.videoSurprise me

Progressive Performance (Chrome Dev Summit 2016)

Progressive Performance (Chrome Dev Summit 2016) on HackerTube: recommended by 4 Hacker News commenters across 4 separate months, 2016–2018.

Chrome for Developers

talk · intermediate · dated

Open on YouTube

Alex Russell's Chrome Dev Summit 2016 talk on building web experiences that work on slow, flaky networks and low-power devices. It argues developers should focus on the performance of real-world mobile hardware rather than desktop machines.

Why Hacker News recommends it

HN commenters cite it as the clearest case for why mobile devices are slow and why code-splitting and progressive web apps are needed.

people recommended it
4
separate months
4
strong recommendations
1
discussed on HN
2016–2018
“Take a look at this talk on why mobile devices are so much slower than desktop devices”
— inian, Dec 2016, in “Things I learnt making a fast website”

What HN commenters said

4 Hacker News comments link this video. Each one links back to its thread.

ferossSep 2018Strongly recommends

Alex Russell first diagnosed this problem at Chrome Dev Summit in 2016 in a really amazing talk: ▶ this video He makes the point that lots of JS frameworks are so large that you're already doomed before you write the first line of real "app code". The framework itself has already blown your performance budget.

in “The “Developer Experience” Bait-And-Switch” · View on HN

scribuFeb 2017Recommends

Those words are meant for people who have the question "why should I go through all this trouble to implement this pattern?" That said, it is very vague. I think this presentation from Alex Russell does a much better job of demonstrating the need for progressive web apps: ▶ this video

in “The PRPL Pattern” · View on HN

inianDec 2016Recommends

Take a look at this talk on why mobile devices are so much slower than desktop devices ( they are indeed 10x slower in the traces I have looked at too) - ▶ this video Also look at the speedometer benchmark ( [link] ) for a more realistic comparison of how slow your mobile device is compared to your desktop when running real world apps. Here are some numbers from the benchmark from some devices - [link]

in “Things I learnt making a fast website” · View on HN

ToucheNov 2016Recommends

Note that you should not choose Ember if you are creating an app intended to be used on mobile, as it doesn't yet have code-splitting. This talk explains about why this is a hard requirement: ▶ this video

in “Choosing Ember over React in 2016” · View on HN

Topics & tags

Web developmentSoftware performance & optimizationmobile webcode splittingprogressive web appsjavascript frameworksslow networks