developer.chrome.com/blog/extende...
We're looking for feedback to support launching this in Chrome. Have you experimented with it? Do you have any feedback (good or bad)? Hit me up!
developer.chrome.com/blog/extende...
We're looking for feedback to support launching this in Chrome. Have you experimented with it? Do you have any feedback (good or bad)? Hit me up!
It is not *my* problem.
It is not *my* problem.
bsky.app/profile/thes...
I looked it up and yep.. www.gamedeveloper.com/game-platfor...
bsky.app/profile/thes...
I looked it up and yep.. www.gamedeveloper.com/game-platfor...
I'm really excited about this one. We're experimenting with the style and trying to focus more on developer questions.
I'm really excited about this one. We're experimenting with the style and trying to focus more on developer questions.
blogs.windows.com/msedgedev/20...
www.youtube.com/watch?v=WmFY...
blogs.windows.com/msedgedev/20...
www.youtube.com/watch?v=WmFY...
Perfect time to level up your React & Web Perf skills 💪🏼
There is also a secret code to turn it into 50% if there is a need 😉 Look for it in the FAQ section of the websites 👇🏼
Perfect time to level up your React & Web Perf skills 💪🏼
There is also a secret code to turn it into 50% if there is a need 😉 Look for it in the FAQ section of the websites 👇🏼
... listen to Steve Wozniak.
... listen to Steve Wozniak.
“[...] we would welcome contributions to integrate a performant and memory-safe JPEG XL decoder in Chromium. In order to enable it by default in Chromium we would need a commitment to long-term maintenance.”
groups.google.com/a/chromium.o...
“[...] we would welcome contributions to integrate a performant and memory-safe JPEG XL decoder in Chromium. In order to enable it by default in Chromium we would need a commitment to long-term maintenance.”
groups.google.com/a/chromium.o...
Here’s the first one: youtu.be/H2naJinRzDA
Here’s the first one: youtu.be/H2naJinRzDA
Would this feature be useful to you?
Would this feature be useful to you?
@nomster.bsky.social @foolip.org and @dbaron.org presented these at W3C TPAC annual meeting last week
More details here:
github.com/WICG/declara...
1/6 🧵
@nomster.bsky.social @foolip.org and @dbaron.org presented these at W3C TPAC annual meeting last week
More details here:
github.com/WICG/declara...
1/6 🧵
It includes a new set of options for your webperf traces — including saving sources & source maps:
developer.chrome.com/docs/devtool...
This makes it easier for those viewing traces outside of the page load to get more context.
It includes a new set of options for your webperf traces — including saving sources & source maps:
developer.chrome.com/docs/devtool...
This makes it easier for those viewing traces outside of the page load to get more context.
Then plus 1 this bug:
issues.chromium.org/issues/34649...
It's one of the things we're considering working on next but need to see that the interest is there, and it's not just a thing I'd like to see...
Then plus 1 this bug:
issues.chromium.org/issues/34649...
It's one of the things we're considering working on next but need to see that the interest is there, and it's not just a thing I'd like to see...
https://www.youtube.com/watch?v=A6rO9RGmJgA
https://www.youtube.com/watch?v=A6rO9RGmJgA
www.debugbear.com/html-size-an...
www.debugbear.com/html-size-an...
• The sale begins Monday, November 24th and runs through December 3rd
• CSS for JavaScript Developers will be 40% off (US$399 → US$239)
• The Joy of React will be 42% off (US$599 → US$349)
• Get ‘em both for 50% off (US$998 → US$499) ✨
• The sale begins Monday, November 24th and runs through December 3rd
• CSS for JavaScript Developers will be 40% off (US$399 → US$239)
• The Joy of React will be 42% off (US$599 → US$349)
• Get ‘em both for 50% off (US$998 → US$499) ✨
It's time to let this go, bc TIL the spec lives at "/css-variables". 😂
Here are some more convincing arguments to call them whatever you like.👇
blog.kizu.dev/css-variables/
Nothing in production to share yet, but shows HTML responses being ¼–⅓ the size of @netlify.com's dynamic Brotli-compression.
~4-6kb per page inc. inlined CSS, before any tuning 🤯
[1]: chromestatus.com/feature/5124...
#webperf
Nothing in production to share yet, but shows HTML responses being ¼–⅓ the size of @netlify.com's dynamic Brotli-compression.
~4-6kb per page inc. inlined CSS, before any tuning 🤯
[1]: chromestatus.com/feature/5124...
#webperf