Adam Rackis

Unexpected Ballmer peak

How has this not leaked by now

Introducing Zustand (State Management) Zustand is a minimal, but fun and effective state management library which just may improve your render performance.

Zustand is one of those wonderfully simple, fun tools you get hooked on pretty quick.

I can't believe it took me this long to discover, but I wrote up a quick intro on it. Better late than never 😬

frontendmasters.com/blog/introdu...

WHO DOESN'T :D

Sorry to be dumb but what does AI have to do with this?

AI is evolving at a terrifying rate

stay mad 😘

hahahahahaha

I just had my first angry reply-guy in my mentions!

Bluesky is maturing!

Congrats y'all 🚀

Oh no a useless reply guy doesn’t like me what will I do 😬

no u

Holy shit you're pressed we don't run into re-render perf issues lmaoooooo

I don't use Zustand at all at work. I just work with talented engineers so I never, ever deal with render perf problems. That's why I was wondering what I was wondering 🤷‍♂️

Idiotic comparison nicely done

Rerender perf has never ever been an issue for me, rerender issues are easily solved with tools like Zustand, so yeah I was curious whether Compiler was worth the effort. Sorry that makes you so mad lmfao

No I work with talented engineers. It just doesn't come up for me 🤷‍♂️

I work on an old React app at scale with zero Zustand. I never deal with rerender perf issues. Maybe you just have skill issues

No, because re-renter performance is never an issue for me

It wasn’t an issue. I was observing re-renders to compare vanilla react to Zustand and was surprised. That’s all 😂

damnnnn you're really worked up 😂

Hahaha stay mad weirdo

lol fuck off I didn’t call out anything I asked a question about re-renders. I didn’t know the answer because re-renders are something that never, ever comes up for me 😂

Hi 👋

Thanks a ton for confirming what @acemarke.dev surmised. It was a long time ago and yeah, now it all makes sense 🚀

My god thank you so much!!!!!

Interesting, so this would only matter if this component had state _other than_ the memoized context data?

Then that other state changing would not affect the memoized context, and so context providers would NOT re-render when that other state changed?

Bam - thank you! More engagement on Twitter, but this zero'd in on it. Thank you so much!!!!

Does that advice presume that you'll have memoized components underneath the context provider, so that passing the memoized context value won't break those components' memoizations?

I have a question about, of all things, React

I'm 99% sure I remember a highly respected React core member (Sophie) advising that you memoize context values to help avoid re-renders.

BUT in my own testing it seems this component's *parent* re-rendering always re-renders this, and all its children

I know the folks who built it are smarter than I'll ever be but I can't help but think the React compiler was kind of a waste of resources

- Superfluous re-renders are very, very rarely an actual perf problem

- Tools like Zustand let you tame re-renders while *improving* dx

Suhail on X: "PSA: there’s a guy named Soham Parekh (in India) who works at 3-4 startups at the same time. He’s been preying on YC companies and more. Beware. I fired this guy in his first week and told him to stop lying / scamming people. He hasn’t stopped a year later. No more excuses." / X PSA: there’s a guy named Soham Parekh (in India) who works at 3-4 startups at the same time. He’s been preying on YC companies and more. Beware. I fired this guy in his first week and told him to stop lying / scamming people. He hasn’t stopped a year later. No more excuses.

x.com/suhail/statu...