Media Summary: Ada (from Samsung Internet) and Jake (not from Samsung Internet) chat about issues with managing Jake and Surma chat about layouts that put the content in charge, vs layouts that put the In this episode, Jake and Surma discuss the array function reduce(). Is it

Is Css A Bad Idea Is Inlining The Way Forward Http 203 - Detailed Analysis & Overview

Ada (from Samsung Internet) and Jake (not from Samsung Internet) chat about issues with managing Jake and Surma chat about layouts that put the content in charge, vs layouts that put the In this episode, Jake and Surma discuss the array function reduce(). Is it You've seen loads of counter tutorials online, but they're all a bit Surma and Jake take a look at 'weak' JavaScript, specifically WeakMap, WeakSet, and the new and shiny WeakRefs. Surma ... Bramus schools Jake about all the viewports that exist in the browser. If you've had layout issues with position fixed, vw units, ...

Jake and Cassie (still from off of Greensock) talk about DOM ready events, which can slow down your app in unexpected In nodejs you can 'require' JSON. The same feature was added to the HTML spec, but then… it was removed. Jake and Surma ... Turns out it's impossible to cross-fade two DOM elements unless they're opaque. Here's why, and a new feature that could fix it. Building consistent, accessible and fast user interfaces is so hard there's an entire profession dedicated to it. One of the problems ... SerenityOS is open source on GitHub: Follow me on Twitter: ... Style definitions are ordinarily written in external .

In this episode, Jake makes the case that URLs are impossible for humans to interpret, especially when it comes to security. How do you take an image with 256 shades of grey and map it to an image with just two colors? Jake and Surma

Photo Gallery

Is .css a bad idea? Is inlining the way forward? | HTTP 203
Avoiding layout shift by putting the CSS in charge - HTTP 203
HTTP 203: CSS Triggers (S1, Ep1)
Is reduce() bad? - HTTP 203
Top 10 performance pitfalls - HTTP 203
JavaScript counters the hard way - HTTP 203
Weak JavaScript - HTTP 203
Inline CSS: What Is It?
It's viewports all the way down | HTTP 203
DOM ready events considered harmful | HTTP 203
Changing web standards - HTTP 203
Slashing layout cost with content-visibility - HTTP 203
View Detailed Profile
Is .css a bad idea? Is inlining the way forward? | HTTP 203

Is .css a bad idea? Is inlining the way forward? | HTTP 203

Ada (from Samsung Internet) and Jake (not from Samsung Internet) chat about issues with managing

Avoiding layout shift by putting the CSS in charge - HTTP 203

Avoiding layout shift by putting the CSS in charge - HTTP 203

Jake and Surma chat about layouts that put the content in charge, vs layouts that put the

HTTP 203: CSS Triggers (S1, Ep1)

HTTP 203: CSS Triggers (S1, Ep1)

How do you know if a

Is reduce() bad? - HTTP 203

Is reduce() bad? - HTTP 203

In this episode, Jake and Surma discuss the array function reduce(). Is it

Top 10 performance pitfalls - HTTP 203

Top 10 performance pitfalls - HTTP 203

Jake & Surma

JavaScript counters the hard way - HTTP 203

JavaScript counters the hard way - HTTP 203

You've seen loads of counter tutorials online, but they're all a bit

Weak JavaScript - HTTP 203

Weak JavaScript - HTTP 203

Surma and Jake take a look at 'weak' JavaScript, specifically WeakMap, WeakSet, and the new and shiny WeakRefs. Surma ...

Inline CSS: What Is It?

Inline CSS: What Is It?

Inline CSS

It's viewports all the way down | HTTP 203

It's viewports all the way down | HTTP 203

Bramus schools Jake about all the viewports that exist in the browser. If you've had layout issues with position fixed, vw units, ...

DOM ready events considered harmful | HTTP 203

DOM ready events considered harmful | HTTP 203

Jake and Cassie (still from off of Greensock) talk about DOM ready events, which can slow down your app in unexpected

Changing web standards - HTTP 203

Changing web standards - HTTP 203

Something a bit different for

Slashing layout cost with content-visibility - HTTP 203

Slashing layout cost with content-visibility - HTTP 203

Jake makes a quick change to the

Importing JSON - ABANDONED - HTTP 203

Importing JSON - ABANDONED - HTTP 203

In nodejs you can 'require' JSON. The same feature was added to the HTML spec, but then… it was removed. Jake and Surma ...

Cross-fading DOM elements | HTTP 203

Cross-fading DOM elements | HTTP 203

Turns out it's impossible to cross-fade two DOM elements unless they're opaque. Here's why, and a new feature that could fix it.

Is CSS-in-JS Really That Bad Idea? Andrey Okonetchnikov

Is CSS-in-JS Really That Bad Idea? Andrey Okonetchnikov

Building consistent, accessible and fast user interfaces is so hard there's an entire profession dedicated to it. One of the problems ...

Browser hacking: CSS padding on inline elements

Browser hacking: CSS padding on inline elements

SerenityOS is open source on GitHub: https://github.com/SerenityOS/serenity Follow me on Twitter: ...

Inline vs Internal vs External CSS

Inline vs Internal vs External CSS

Style definitions are ordinarily written in external .

Humans can't read URLs. How can we fix it? - HTTP 203

Humans can't read URLs. How can we fix it? - HTTP 203

In this episode, Jake makes the case that URLs are impossible for humans to interpret, especially when it comes to security.

Dithering - HTTP 203

Dithering - HTTP 203

How do you take an image with 256 shades of grey and map it to an image with just two colors? Jake and Surma