Pinned
Ryan Carniato
@RyanCarniato
- I still find it crazy how we are still discovering primitives that completely collapse decades of carefully crafted imperative code. This article is probably more impactful as a live demo. But picture it paints is still very powerful.Part Two of @RyanCarniato's in-depth look at Solid 2.0's Async shows how having the right primitives lets you skip the rewrite. Your client-only app was the optimistic UI all along. It just wasn't aware of the server yet. solidjs.com/blog/async-sol…
- Fabian's framework-agnostic work is top-notch. I love to see the democratizing effect libraries like this have.Formisch v1 is here. 🎁 A schema-first form library for 8 frameworks: React, Vue, Svelte, Solid, Angular, Qwik, Preact & React Native. ✅ One Valibot schema = types + validation ✅ Native performance across all 8 frameworks ✅ Headless — works with your existing UI ✅ Bundle
- Help him out. I've been wondering about this too. I always hear it from React devs but it honestly stumps us. Is there a pattern people use with Signals that we aren't accounting for?One thing I dont get. What is this "accidental tracking" people talk about in @solid_js
- For those looking for more details after the release announcement here they are. Solid's approach to Async is one of kind. And more than that it has real implications.Check out this in-depth look by @RyanCarniato at what makes Solid 2.0's async approach uniquely powerful. Part 1 of 3. solidjs.com/blog/async-sol…
