2. Pattern matching seems pretty non-controversial. What’s holding it up? Flow even shipped it!
3. Shared immutable data across workers is hard so I get it, but we could at least ship something in the meantime?
1. Pipe operator (any variant)
2. Pattern Matching
3. Some kind of shareable immutable data (records, structure, whatever)
Congrats to my coworker @ashley-c.bsky.social at TechAtBloomberg on advancing Await Dictionary to Stage 2.7 at TC39 today 🎉
Promise.all returns positional results as an array. Promise.allKeyed allows named results inside an object 👍
github.com/tc39/proposa...
2. Pattern matching seems pretty non-controversial. What’s holding it up? Flow even shipped it!
3. Shared immutable data across workers is hard so I get it, but we could at least ship something in the meantime?
1. Pipe operator (any variant)
2. Pattern Matching
3. Some kind of shareable immutable data (records, structure, whatever)
Congrats to my coworker @ashley-c.bsky.social at TechAtBloomberg on advancing Await Dictionary to Stage 2.7 at TC39 today 🎉
Promise.all returns positional results as an array. Promise.allKeyed allows named results inside an object 👍
github.com/tc39/proposa...
1. Pipe operator (any variant)
2. Pattern Matching
3. Some kind of shareable immutable data (records, structure, whatever)
The edges were sharp and the background blurry.
iOS26 / macOS 26
The edges are blurry and the background warped.
The edges were sharp and the background blurry.
iOS26 / macOS 26
The edges are blurry and the background warped.
Waku
redwoodSDK
React-router (beta)
Any other frameworks that support RSCs?
Waku
redwoodSDK
React-router (beta)
Any other frameworks that support RSCs?
Am I upset about it? Also no.
Am I upset about it? Also no.
Range syntax for style queries and if() functions has shipped in Chrome!
Check it out:
una.im/range-style-...
Range syntax for style queries and if() functions has shipped in Chrome!
Check it out:
una.im/range-style-...
www.theguardian.com/world/2025/n...
www.theguardian.com/world/2025/n...
But aside from that, can we stop using top level await entirely? It makes things so so annoying.
The module graph fails in cases where two modules import a third at the same time. Demo: random-stuff.jakearchibald.com/bug-repros/t...
It's best to avoid the feature for now 😔
But aside from that, can we stop using top level await entirely? It makes things so so annoying.
lit.dev/blog/2025-10...
Honestly, I forgot I was on a podcast because it was so fun to chat.
w/ guest @nmn.bsky.social
Rust, StyleX, Swift, whiskey and whatnot
nerdy.dev/www-ep215-ru...
Honestly, I forgot I was on a podcast because it was so fun to chat.
You just have to call the fn manually. It’s not reactive anymore. Still declarative though.
As far as I remember, we already tried that
See, for example, this BackboneJS counter
You just have to call the fn manually. It’s not reactive anymore. Still declarative though.
So usually, I’ll use the shiny new features such as relative colors with a fallback. And for the fallback, I almost always still reach for the rgba()/hsla()
Instead, I will recommend anyone who uses hsla() or rgba() to read this article, as even the comma-separated syntax is now legacy.
piccalil.li/blog/a-pragm...
So usually, I’ll use the shiny new features such as relative colors with a fallback. And for the fallback, I almost always still reach for the rgba()/hsla()
for hover state im doing `:has(*:is(.sidebar-icon-trigger:hover`
made only using css. no js listener used. took me longer than i thought it would.
- the event APIs are good. A single “on” prop makes a lot of sense. Funnily enough, it Feels like a router!
- the “router” API is good with some obligatory boilerplate. It’s usually worth it but developers will be turned off by it.
- the event APIs are good. A single “on” prop makes a lot of sense. Funnily enough, it Feels like a router!
- the “router” API is good with some obligatory boilerplate. It’s usually worth it but developers will be turned off by it.
Vite unbundled mode kinda sucks.
This would give us the build time benefits without the network request overhead.
github.com/tc39/proposa...
Vite unbundled mode kinda sucks.
This would give us the build time benefits without the network request overhead.
A simple line of modern CSS to create a conditional Border Radius. The value will adjust based on either the container width or screen width.
css-tip.com/conditional-...
cc @ishadeed.com @una.im