I might have a new favorite state manager...

[@tinrab]

Just one more state manager guys and all will be good.

[@lovebes]

bruh just one more state mamager bruh I promise bruh this is the last one bruh

[@twisterrjl]

just one more, c'mon

[@ArcticPrimal]

Just waiting for a state manager to become a framework similar to how react router became a framework

[@ChiragAgg5k]

zustand is always gonna be my go to

[@spicepirate]

me too 👍

[@philheathslegalteam]

Jotai

[@FusionHyperion]

Pinia is great for vue

[@trappedcat3615]

Why don't we call state managers governors?

[@johnlombardo]

State Comptroller?

[@Jenkkimie]

Mayors. Most countries don't have governors separately but every country has mayors.

[@rahu1gg]

For a 4 mins read blog post it took 22 mins youtube video

[@ThinkleTink]

At this point I think he does it to ensure the ragebait posts and clicks

[@witchmorrow]

but that's a good thing, that's entirely the point - he's adding useful comments and pointers. If you don't find his commentary useful then why are you subscribed...

[@ThinkleTink]

@@witchmorrow The format used to be shorter, now it feels like the viewer is being strung along just to always hit that 30 minute video mark or close to there.

[@javierflores09]

Brother just read the article if you don't like the commentary, because that's like the whole point of this channel

[@ThinkleTink]

@javierflores09 K

[@guxit]

Valtio is an overlooked state manager that would simplify that agora zustand entanglement. People seem to avoid it because it's so simple. That's why I like it though.

[@someDudeOnYtb]

Recently discovered it working on a react native project and I think I will start using it in everything,react or vue or vanilla

[@offlercrocgod]

As a few of the comments already mentioned just use signals, legend-state in React and the other frameworks have signals built-in

[@Dimonina]

New store again... My opinion is not popular, but rxjs in angular has solved all of these store problems many years ago out of the box, but the only problem is that it is difficult to learn for the majority. However, React is a super popular framework, why just can't anyone figure out a versatile solution that just works, but still we have "store" and the functions to update it, but just different syntax. The approach remains the same. This is the biggest problem imo.

[@menmikimen]

True, angular is really good in this regard. And now, for non-complex problems, it is possible to use signals instead. ❤

[@tvujtatata]

Better than being forced to used a single opinionated option or writing own. What have you done for the community?

[@ivanmaglica264]

I love injectable services in Angular

[@adityaanuragi6916]

I'm a React dev and am eager to learn Angular I just need to have discipline cuz I've heard its difficult at the start but lovely later

[@abui6914]

Trust me guys react is one state manager away from perfection

[@oddfeeling7956]

I don't know why I find this funny

[@rajikkali2381]

Pinia ❤

[@aghileslounis]

lol

[@salva-dev]

Very interesting... Thanks. I will try it. You should also try nanostores, from Evil Martians, super lightweight and framework independent store.

[@Infinitay]

Are state managers the new front end framework meta?

[@jatiquep5543]

I will never leave zustand ❤❤❤

[@ldlework]

Zustand is the last state manager needed. Simple as.

[@UliTroyo]

Heck yeah! I ran into David K Piano's first talk about XState years ago while looking for state machine content. I use it with Svelte for heavy UI logic.

[@guillemgarcia3630]

man all of this is so easy in solidjs, this vid makes me appreciate it even more

[@luka1790]

This

[@philheathslegalteam]

FYI you can infer a key’s existence in the same object. Both Stiches and my library TW Classed rely on this. But it’s like you say HELLL to infer those types.

[@ArcticPrimal]

The author is right it's zustand with redux toolkit features to overcome zustand's shortcomings

[@orlvni]

react context + our own state machine for life

[@buthow900]

Have you seen ombistac zedux?

[@markosunbro2732]

They will do everything to not use signals )))

[@termorey]

Effector (and ecosystem) is the best for me in most cases

[@alec-dora]

Which mac are you using?

[@St0rMsk]

That Leo meme from once upon a tim e a hollywood, poining on a TV and titled: Tha'ts PINIA, that's pinia for React

[@toutpt]

I believe it is easy to implement an event driven state mngt based on the Dom 😅 I don t say it should be like this but it just work.

[@ronny584]

Theo has bless us with a 23 minutes video and not 3hrs, thank goog.

[@kennyPAGC]

As a django dev who embraced nojs philosophy years ago I am SO happy when I see videos like this.

[@StephanHoyer]

Again a problem you would not have if you would not diff a change twice in react. Just drop setState and redraw the whole thing.

[@FusionHyperion]

TLDR: Basically Pinia

[@returnZeroo]

I will stay with jotai

[@lonewolf36s]

pretty much everything i have is in redux. So many slices... Maybe in future on a new project i'd try this. It looks REALLY clean.

[@notarealperson9709]

Hypermedia as the engine of application state (HATEOAS)

[@Ked_gaming]

99% of the time you dont need a store, dont thank me

[@frusen_sol]

*preact-signals* my favorite one

[@ArcticPrimal]

Just waiting for a state manager to become a js framework similar to how react router

[@snowofice]

Zustand sounds German (translates to status) and as such you should propably pronounce it more like tsustant.

[@nathanaelbennett8286]

state management considered harmful

[@alihassn4112]

WTF, every day there's a new state manager? What a crap to be a JS developer, long live Laravel!

[@twilightdev]

stores popping out more often than js frameworks (well technically they are js frameworks too but still)

[@rickdg]

reset the counter

[@arpitbharti6245]

nope zustand has all these features

[@MirkoVukusic]

I'm on Legend State and don't see a reason o change

[@lqhuy]

Look at Legend State

[@johnlombardo]

I usually enjoy your videos as a background task but this had my full attention. Saved to watch again 👍🏼

[@nChauhan91]

Been using it for 3 years in a project, it's good for things but I wouldn't recommend it for general state management

[@graficandorealidades7561]

Thanks, you saved me 22 minutes of my life

[@t3dotgg]

xstate-store is not 3 years old and is very different from traditional xstate

[@nChauhan91]

@@t3dotgg my bad, I thought this was just xState library that David created.

[@jatiquep5543]

​@@t3dotgg he should have called it another name as a new library

[@johnlombardo]

@@jatiquep5543 What, like XStore? Or my suggestion, Store Manager For People That Like How XState Works.

[@KopoLPedov]

reatom is the best, but not hyped

[@jotaroisdarius1918]

DAMN IT THEO, IT'S TSOO-shtahnt NOT ZASTEND cool video tho 👍

[@random-i2s]

Why is the FE world like this? Why do we need a new framework, state manager, editor, runtime, additional languages on top with build steps nonsense every single day? In the backend world languages has left these trivialities behind and for example go, c#, php, java communities are not into this at all . They focus on the things that matter which means we have a stable environment with mature tooling

[@zenpool]

if it looks like zustand why bother 🤷🏼

[@fazamaza801]

Guys just literally reinvent redux toolkit, LMAO

[@ArianvanPutten]

Please don't pronounce Zustand like that it hurts my soul The u is pronounced as o in the word "zoo" The Z is pronounced as "ts" Ts oo stand

[@alexey9796]

nah

[@alek282]

First, go Theo

[@mindblower113]

I really liked Redux Toolkit.

[@diadetediotedio6918]

Would not it be clearer in react if you just made an utility, like: function effect({ deps, run, cleanup }: { deps: any[], run: () -> void, cleanup: () -> void }) { useEffect(() => { run(); return cleanup; }, deps); } that you can then use like this: effect({ deps: [slug], run: () => { ... }, cleanup: () => { ... } }) I feel like at least some of the problems with useEffect is that it is too much quirky to use, so wrapping it maybe provide some benefits.

[@requindr]

I feel like you shouldn’t do a wrapper that doesn’t provide benefits, at best it will only confuse other devs

[@diadetediotedio6918]

@@requindr My whole point is that it does provide benefits (semantic ones), lol. And if someone gets confused by this I don't think this person is a programmer, those are literally plain english words with well defined meanings in react, I'm not presenting a theorem proof in modal logic.