JavaScript fwdays'20
2020-03-14
-- online --
who it's for
web developers, frontend developers, React developers, performance engineers, build and tooling engineers, browser engineers
topics
heavy client JavaScript costs; static HTML and SSR tradeoffs; Next.js and pre-act experiments; concurrent React scheduler; Suspense and React priorities; webpack plugin performance tuning; critical CSS extraction and purgecss; bundle analysis and visualizers; DevTools Flexbox and Grid inspectors; Google Search Web Rendering Service
| title | author | length |
|---|---|---|
| Did we(b development) lose the right direction? | Stefan Judis | 54m |
Claim: heavy client JavaScript often harms users more than it helps. Evidence: a cutting‑edge personal site ships 340KB index.html with 22 inlined articles and… | ||
| Building the web in the web | Sara Vieira | 33m |
Builds a small React app in CodeSandbox that fetches Kanye West quotes from a free REST API, styles it, commits to GitHub, opens a pull request and triggers a… | ||
| The best is yet to come: the Future of React | Matheus Albuquerque | 39m |
Shows concrete experiments: an app defers analytics with unstable_scheduleCallback at low priority and raises FPS above 50, demonstrating that concurrent React… | ||
| DevTools, more than just a debugger | Chen Hui Jing | 36m |
Shows concrete DevTools actions and surprising outcomes: the Flexbox inspector reveals that Flex basis is a starting size not final, and setting flex-basis: 0… | ||
| I Tried 200 Webpack Plugins for Performance (So You Don't Have To) | Yvan Akulov | 34m |
A survey of about 200 webpack plugins focused on web performance, reviewing useful loaders and plugins for deep minification, image transformation, and… | ||
| HTML: The Good Parts | Vadym Makeev | 01h 05m |
Examines concrete HTML practices: shows a conference schedule mistakenly built from 270 divs instead of a table, demonstrates that browsers parse HTML… | ||
| How Google Search renders the web - a look behind the curtain | Martin Splitt | 34m |
Google Search uses a Web Rendering Service that runs headless evergreen Chrome in a managed pool, collects a render tree not pixels, and intentionally skips… | ||
| nothing matches | ||