Josh Claunch

@darthcaro Zoysia grass is actually amazing and grows so well here. ... Unfortunately somebody from the St Augustine grass dept must be paying off all the HOAs 'cause they all ban Zoysia.

i am so jealous of yall in utah and idaho that have beautiful soft grass you can just lie down on. floridian grass is nasty and nobody ever lies down on it. 🥲

@s4nyxx 👀

Zedux now rivals most signals libs for speed. That's crazy considering its feature set. MobX is the only signals lib with comparable features, but Zedux is more than twice as fast. github.com/Omnistac/zedux…

@hamzajsx TS, suspense, modularity (atoms are king for microfrontends), naturally memoized derivation tree, scalable architecture that isolates updates. The maintainer of Zustand literally created Jotai to address Zustand's shortcomings esp. with memoized state derivations

@josh_claunch how is jotai more powerful than zustand?

I'm thinking of add redux to a @reactjs project ... is Redux still cool in 2025?

@FinancialPhys Same! I moved to a new town, finally picked a dentist and he said I had 14 cavities. I made 2 appts to fix them all. First appt was horrible, so I went to a different dentist for the rest. And he was like, "Umm, you don't have any cavities, your teeth are amazing."

A patient cured is a patient lost

@Xayide2_07 @eloffd @DelusionPosting 💯 This explanation is just missing something about midichlorians and the chosen one

@eloffd @DelusionPosting She took "abstinence" in the birth control methods and said it could fail. Well, it seems there was one case like that, little bit more then 2000 years ago, but exempt that, it's pretty sure you wont get pregnant if you stay abstinent.

@vadi_ms Hey, yes, replied here: #discussioncomment-12916365" target="_blank" rel="nofollow noopener">github.com/Omnistac/zedux…

@josh_claunch Is ot possible to have easily the same state across extension, webpages and injected data on some pages?

@helloumma It's several orders of magnitude faster than shuttling updates between two (much slower) tools. We move enough data that using UI state to reduce the amount of server-side logic needed reduces our operating costs significantly.

@helloumma Depends on the app. RQ+Jotai is a great combo in many cases It wasn't an option for us with sockets moving lots of data. We use Zedux which combines cache management and UI state management in a single atomic model And I'm pretty much all-in on TanStack Start at this point

@DavidKPiano He-hey! Just goes and does it. Legend 🎉 So now, actually, I officially like your API better than nanostores and will probably recommend it instead.

@josh_claunch Thanks for the heads up, btw; made some architectural improvements (including solving the diamond dep problem) here: github.com/statelyai/xsta…

Today would be a weird day to announce that XState Store now has atoms, so I'll wait until tomorrow

@DavidKPiano You're correct that "atoms" is a loose term. However, all libs but yours have an implicit reactivity baseline, namely handling the diamond problem at least. You just described recursive observables, not an atoms implementation. I recommend this article: dev.to/milomg/super-c…

XState Store atoms, at least at a basic level, are graph-aware. Creating a "combined atom" tracks dependencies. Keeping it simple for now. Our atoms fit the concept of atoms in these libraries. Also note that none of the libraries you mentioned give a comprehensive, explicit definition of an "atom".

@tannerlinsley @PatrikarSanket @garyfung @jherr @jamonholmgren Well that is the problem - React can't implement RSCs, so they have no business telling frameworks to. The rollout was always doomed React should have said, "Hey framework authors, here are some APIs that can help with your server-side features. Let us know if you need more"

@PatrikarSanket @garyfung @jherr @jamonholmgren My opinion is just as nuanced as the use cases and tech behind RSC. I love the premise and what it would allow, but I'm not happy with the marketing/execution/rollout so far.

I don't really understand the RSC hate. You're getting angry at a tool. If you don't need it, just don't use it. RSC is just another option for serializing and hydrating JSX and interactive components. I get that the NextJS App Router approach to using the RSC functionality might not have worked in your use case. And that's totally valid take. But it's not a reason to hate the underlying tool. Not all tools work on all jobs. There are lots of ways to use the underlying RSC functionality, and we are just starting to see those come out. For example; a SPA application could make a server call and get back Flight data (the format of RSCs) and hydrate that on the fly, loading in the interactive code only when necessary. This would reduce bundle size dramatically and speed up the initial load of the app. And that's just one of many possible options to leverage RSC. Has it taken too long to get to RSC options outside of the App Router model? Perhaps. But RSC is a major addition to the underlying React toolkit, so of course it's going to take a while for framework authors to understand it and to see if it fits their model, or not. But I don't think it's helpful to just hate on RSCs entirely because you don't dig the NextJS App Router. If the App Router isn't matching your use cases don't use it. There are new models of RSC interaction on the way, from Waku and @tan_stack Start. And those might provide you options based on RSCs that do work for you. Or not. Either way, RSC support existing in the framework does not hurt your SPA app.

@vadi_ms @hsnice16 I can provide examples and a more long-form response tailored to your setup if you start a discussion in the repo here: github.com/Omnistac/zedux…

@vadi_ms @hsnice16 Good question. There are lots of ways to set up sockets, so it's hard to commit to a direction for a guide. We have kafka topic "endpoints" and set up one "stream" atom per topic. Some atoms take requestParams, which create one instance of that stream atom per set of params

I banged my head for so long on recoil with the latest next.js, just to find out that it is not compatible. heck!

@vadi_ms @hsnice16 I'll get a real doc. Gist: It's 10x faster. It's a cache manager like React Query. It has real DI. Cached atoms are discoverable and universally snapshottable/restorable. This model works better across realms, e.g. with SSR and multi-window fintech setups.

@josh_claunch @hsnice16 What are the main advantages of Zedux in comparison to Jotai

@akshxdevs Recoil isn't maintained anymore. It doesn't work with React 19 and probably never will. But it's okay! Jotai and Zedux have been much more powerful and stable than Recoil for years now. They're both excellent alternatives.

Next.js 15 has some wild errors—Recoil isn’t even experimentable! 🤯🔥 Anyone else feeling the pain? 💀 #NextJS #Recoil #DevStruggles #WebDev

@engjames256 TSQ is a cache manager. React Context is a DI tool. Jotai is easily the best state manager on this list.

React Devs: What's your favourite state library? - Redux - Zustand - Jotai - ContextAPI - Tanstack Query