Josh Claunch

React/TypeScript nerd with a computer and too many ideas.

Coding minion.

Creator of and the occasional piece of music 🎵🎵🎵

[Josh Claunch @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.

[Josh Claunch @josh_claunch]

@s4nyxx 👀

[Josh Claunch @josh_claunch]

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.

https://t.co/dxDpV5PRnL

[Josh Claunch @josh_claunch]

@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 @josh_claunch]

@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."

[Josh Claunch @josh_claunch]

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

[Josh Claunch @josh_claunch]

@vadi_ms Hey, yes, replied here: https://t.co/lcxTliTRYB

[Josh Claunch @josh_claunch]

@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.

[Josh Claunch @josh_claunch]

@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 @josh_claunch]

@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:

https://t.co/4DNiGVsqLj

[Josh Claunch @josh_claunch]

@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"

[Josh Claunch @josh_claunch]

@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: https://t.co/e9r33yR7Fc

[Josh Claunch @josh_claunch]

@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

[Josh Claunch @josh_claunch]

@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 @josh_claunch]

@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.

[Josh Claunch @josh_claunch]

@engjames256 TSQ is a cache manager. React Context is a DI tool.

Jotai is easily the best state manager on this list.