"Redux requiring boilerplate" does a disservice to modern redux with RTK which is actually quite good. Also, jotai allows you to define setters, and you can use derived atoms to define different methods to interact with the same data.
Well for these technical topics IMHO it'd be much better to whip out the code editor and do some demonstration. But you guys sometimes do this kinda podcast-only so, yeah...
@@_ilearn Yeah, that's why i said it's just my opinion. But I'd bet a beginner (in these technical topics, like in this cases, state management), would struggle with something like "signals" if he's total new to it and try to listen to it only. Would be infinitely hard, don't you think? Again, I didn't even listen to this whole podcast so don't know how detailed they made the talk. Just a constructive feedback.
@@dothex Lately, CJ's been doing how-to videos on subjects that get discussed by Scott and Wes. He hasn't been covering everything, hopefully comments like this will help him prioritize what episodes could use some examples.
I think the term effect comes from "Side effect" which refers to something that should happen alongside the state changing, while you defined it as "listening to state changes". Sorry if I'm over-correcting, it just seemed like an important distinction to me.
![Megan Thee Stallion - Roc Steady (feat. Flo Milli) [Official Video]](http://i.ytimg.com/vi/HozPPyqW0dY/mqdefault.jpg)
"Redux requiring boilerplate" does a disservice to modern redux with RTK which is actually quite good. Also, jotai allows you to define setters, and you can use derived atoms to define different methods to interact with the same data.
Anytime you guys talk about state the videos go crazy up, nice
Also before i even start the video, state stored in url 🎉
great episode! thanks
Well for these technical topics IMHO it'd be much better to whip out the code editor and do some demonstration. But you guys sometimes do this kinda podcast-only so, yeah...
A lot of us listen to it while walking.
@@_ilearn But alot of us want to see this in action as they're describing it.
@@_ilearn Yeah, that's why i said it's just my opinion. But I'd bet a beginner (in these technical topics, like in this cases, state management), would struggle with something like "signals" if he's total new to it and try to listen to it only. Would be infinitely hard, don't you think? Again, I didn't even listen to this whole podcast so don't know how detailed they made the talk. Just a constructive feedback.
@@dothex Lately, CJ's been doing how-to videos on subjects that get discussed by Scott and Wes. He hasn't been covering everything, hopefully comments like this will help him prioritize what episodes could use some examples.
love this!
started front-end, winking at fullstack - state management is the first real issue i'm trying to solve
I think the term effect comes from "Side effect" which refers to something that should happen alongside the state changing, while you defined it as "listening to state changes".
Sorry if I'm over-correcting, it just seemed like an important distinction to me.
They talk more than they build. It’s ok, it’s just for entertainment if you listen for accuracy you’ll have a bad time here lol
No thats other effect
Do you have state with auth like acl
For FormData if you want to just "access" the property just use a proxy. It's pretty straight forward, after you do it the first time 🙂.
With our Big Ball of Mud project, we're leveraging Denial-based state.
RTK!?
What is state? Baby don’t hurt me, don’t hurt me… no more.
Every single time.
Oh ooo oh ooo oh oh
the irony of existing javascript frameworks is that they const and provide function to override its value 😂
React State + React Context + React Compiler is the end game
First? Will update with impressions.
Atoms are best for freelancers 🎉
ayo where's my boy htmx at?
The DOM as state.