Some people were wondering how you could build additional pending affordances or do error handling on top of optimistic data. I'm not a designer but I think this updated demo shows the possibility.

Every action randomly fails 33% of the time.

stackblitz.com/edit/github-...

Streams back tomorrow. Excited to talk about my latest Async Work, my foray into using AI tools, and look at the State of JS Results.

www.youtube.com/watch?v=drLX...

Agreed. This is where the future is.

The stream is back tomorrow. Going to reflect on 2025 and look at what is shaping up in JavaScript frameworks into 2026.

www.youtube.com/watch?v=Z54k...

It's that time of year when I like to reflect (and realize I didn't publish enough articles over the last year).

"JavaScript Frameworks - Heading into 2026"
#DEVCommunity #React #WebDev #JavaScript

dev.to/this-is-lear...

I want to thank @replay-io.bsky.social. I honestly don't know how I would have debugged an issue I had if not for their time travel debugger.

Certain nodes would "stick" after hovering, and required very specific timing to reproduce.

saw a question asking if solid-js is still relevant

frontend talk has been mostly replaced by ai talk but it's quietly grown 6x in a year

in opencode
- tui in solid
- tauri in solid
- web app in solid-start
- enterprise app in solid

Tomorrow's stream we dig into Time Slicing. What does it do? Is it necessary? Are there alternatives?

And look at how the topic impacts the direction of Async Signals.

www.youtube.com/watch?v=YNdr...

What if we didn't time slice and instead went async?
stackblitz.com/edit/github-...

I was trying to re-create Sierpinski's Triangle Demo to look at Time Slicing again and I'm having trouble getting the results I was looking for in React 19. Am I doing something wrong?

stackblitz.com/edit/vitejs-...

The stream is back tomorrow as I dig into what I've been working on in the world of Async & Signals.

www.youtube.com/live/ori9xZh...

here is something that feels so powerful when behavior is baked into the reactivity, rather than compilers or framework. I've remade a few demos trying out the reactivity with manual DOM updates to test it out, starting with Ryan Florence's Select Example
playground.solidjs.com/anonymous/85...

Thoughts on an approach to async in SolidJS that requires no wrappers, compilers, or coloration, non-blocking render, but it requires `setSignal`(& derived) to stay in the past until flush?

1️⃣ <a href="https://poll.blue/p/8LxeIv/1" class="hover:underline text-blue-600 dark:text-sky-400 no-card-link" target="_blank" rel="noopener" data-link="bsky">Yes, seems good
2️⃣ <a href="https://poll.blue/p/8LxeIv/2" class="hover:underline text-blue-600 dark:text-sky-400 no-card-link" target="_blank" rel="noopener" data-link="bsky">Yes, used to it
3️⃣ <a href="https://poll.blue/p/8LxeIv/3" class="hover:underline text-blue-600 dark:text-sky-400 no-card-link" target="_blank" rel="noopener" data-link="bsky">No, React is the worst
4️⃣ <a href="https://poll.blue/p/8LxeIv/4" class="hover:underline text-blue-600 dark:text-sky-400 no-card-link" target="_blank" rel="noopener" data-link="bsky">No, async isn't worth it

📊 Show results

Alright progress. I imagine most won't understand what you are seeing. I had a crazy idea a week ago that all the ideas we have about async could be wrapped into the native behavior of a runtime reactive system. So I dropped what I was doing to test.

playground.solidjs.com/anonymous/c1...

The worst part of API design is when the answer is the one your users will hate. They will never thank you for it. They will misunderstand it until the end of time. But there is some comfort in them never knowing the pain they may have faced.

People give `useEffect` a bad rap, but it isn't usually the source of the problem. The real problem is too many `useState`s.
Devs fail to see how their data is connected and model it too discretely. As those connections appear, it is easier to synchronize than refactor the model. 1/

Reading this I realized I forgot to cross post. But now I don't have to. Dan is absolutely right.

Tanner's concern about overloading an existing platform syntax with new semantics is the best argument against.

But mechanically the shape of the solution fits the problem better than alternatives.

Since people like pictures. I've used this before but this is why I find this direction compelling.

I honestly don't have any ambition left of eCommerce. But I don't want to give up anything on the right side.

Since people seem to interested in alternative Server Component architectures, might as well publish the source. These documents are rough, basically brain dumps. But I think thanks to Tanstack there is interest.

"Isomorphic First Framework"
hackmd.io/@0u1u3zEAQAO...

I'd also thank the lovely community over at @tanstack.com! We know you are a big part of making this happen.

To the continued growth of both our communities. 🥂🍻

New post!

www.lorenstew.art/blog/10-kanb...

Very cool use of the reactive graph to inform preloading. One of the challenges of something like <Activity> for preloading is you need to render the tag (or not). Works great for static, but harder for dynamic like parameterized urls. This data drive approach doesn't care what is downstream.

We're live: twitch.tv/ryansolid

At 11am PT tomorrow, @igorminar.bsky.social and @anfibiacreativa.bsky.social join @tannerlinsley.com and I to talk about Web Fragments, a fresh take on Micro-Frontends.

www.youtube.com/watch?v=sneu...

Thank you everyone who supports the streams. I know my content isn't always the most approachable but the channel has hit 20k subs.

So thank you!