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️⃣ Yes, seems good 2️⃣ Yes, used to it 3️⃣ No, React is the worst 4️⃣ 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!

A lot of conferences going on this week. Join me on stream tomorrow as we talk about it all: www.youtube.com/watch?v=8bpj...

Received this in the mail today for my son. I see the @solidjs.com mascot is alive and well. Thanks @davedbase.com!

It turns children into siblings 🤯. @ryansolid.bsky.social blowing every React dev's mind with nested data fetching and fine-grained reactivity 🔥 www.youtube.com/live/fnyK-xX...

Be honest is this just a bad idea? Future templating while keeping backwards compatibility with current JSX. Is this something people would be interested in? hackmd.io/@0u1u3zEAQAO...

this is worth saying: nuxt is an independent open source project and not directed or owned by any company. check out github.com/nuxt/governa... for specifics. you can see the companies which sponsor the project financially on OpenCollective and GitHub Sponsors.

Going after OSS projects that are openly governed isn't going to do what you want it to. Vercel makes its money from its hosting platform and paid products. OSS is not a paid product and while contributes goodwill doesn't directly impact the bottomline. And these project's reach well exceed Vercel.

We're live: twitch.tv/ryansolid

For the first time in the 4 years I've been doing Friday streams, I will be having a @react.dev Core Team member as a guest. I'm excited to welcome @ricky.fm on to talk all things React. Past, present, future. www.youtube.com/live/3vw6EAm...

Seeing the reaction to the Array primitive in RippleJS, I can't help but feel that maybe React initially taught us the wrong lesson, and Svelte initially taught us the wrong solution to that lesson. Data primitives that are special are allowed to be. It isn't something to be feared.

Growing as a person means using signals... I don’t make the rules @ryansolid.bsky.social does

So nice to finally have this example working again in 2.0 codebase. This might be the last major client side feature I needed to test out on the experimental branch. But it looks like Transitions are alive and well: stackblitz.com/edit/github-...

We're live twitch.tv/ryansolid

There is hate for JS on the server. But none have accomplished what @markojs.com has. Forget Islands, forget serialization boundaries, forget writing code twice. Just declarative templates, low JS, automatically. @dpiercey.me joins me Friday to show how it's done. www.youtube.com/live/x-3RxGf...

@solidjs.com SolidStart has an official roadmap announced 🎉 for the ones who watch: 📺 youtu.be/p3OGfop-mtI?... for the ones who read: ✍️ github.com/solidjs/soli...

⚡ Speaker highlight: Ryan Carniato, Creator of @solidjs.com When talking about what is next in web dev, signals have to be mentioned somehow. And who could it do better than the creator of Solid! @ryansolid.bsky.social will join us remotely as panelist to shed some light on the future of web dev.

Come join me in 30 mins as I talk through redesigning concurrency for Solid 2.0: www.youtube.com/watch?v=eZAc...

I won't be streaming friday as I have previous commitments, but I'm tempted to do an impromptu stream today about designing Transitions. Anyone interested?

It feels great when something you've been working on for weeks finally begins to work. I think I have the start of graph-based Transition entanglement. Clicking the same button multiple times shows entanglement and different buttons parallel Transitions. playground.solidjs.com/anonymous/b7...

I need to remember to talk about this on my next stream. What React is doing is quite logical here. I see a lot of parallels between Actions and useEffect. They break the dependency graph so you can no longer automatically be smart about what they impact.

This Wednesday at 12:00ET we'll be live streaming a conversation with both @ryansolid.bsky.social and @tannerlinsley.com on the JavaScript Jabber podcast! We'll be talking about modern frameworks trends and RPC. It's going to be awesome!

This is a very good thing. I don't think the complaint was silly. It is difficult to know if something is fundamentally slow or if it is implementation. Fortunately @quack.uy, Solid maintainer reported the issue and now it is fixed. For every issue like this there are dozen not so easy to address.

For a framework renowned for its innovation, it is funny how little Solid has changed in the last 7 years. Yeah we've innovated on features, fine-grained concurrency/hydration, streaming, server functions, single flight mutations, but the core tech and structure are untouched.

The dividing point between "Frameworks" vs "Platform Purists" is the belief of whether DOM should be the source of truth for state. Almost every Web Component argument, issue with design comes back to this. You don't need to go any further than Forms to see this in action.

Proxies are so cool. We were talking about removing the need to use `createEffect` in 90% cases in Solid, and I was like "I think we can just proxy refs to avoid mounting effects". Mizulu from Solid community went ahead and put a quick prototype together. playground.solidjs.com/anonymous/45...

Vite: The Documentary premieres October 9th at @viteconf.org in Amsterdam ⚡ youtu.be/46fe5AFc0tY

Suspense, Activity, and other boundaries are fundamentally different than concurrent Transitions. Boundaries are "read"-centric and local. They care about if/when something can be rendered. Transitions are "write"-centric and global. They enable transactional state updates.

We're live twitch.tv/ryansolid