4 ms·
10 years with an unchanged react state model: https://reagent-project.github.io/ https://reagent-project.github.io/
by nathants 4y ago
10 years with an unchanged react state model:
https://reagent-project.github.io/ https://reagent-project.github.io/
- whacked_new 4y agoHaving used reagent, watching the React space evolve is like a bricklayer watching a constant stream of innovations around mud. Sure, you could build foundations with bricks, but why do that when you can use a fancy mold and pour mud into it? Why have clean blocks when you can have sticky, messy, dirty goop? Alas, castles and fortresses have been built with messy goop, and the amount of goop-specific tools and goop slappers far outweigh the bricklayers. So I too slap goop.
- nathants 4y agometaphor of the year!
- shadowgovt 4y agoHave you seen the debugging tools for goop? I mean, they're absolutely necessary because the goop is full of insects. But so elegant!
- nawgz 4y agoThis kind of thing is possible because the React state model ultimately hasn't evolved too much itself; only the easily-accessible user-facing parts of it. I've been running a mobx-react setup for 7 years. It's been thru a few syntaxes but it behaves identically. Minimal rendering, observability, I find it the most intuitive state management pattern.
- nathants 4y agomobx looks the most reagent like state model in vanilla react. my forever setup is here: https://github.com/nathants/aws-gocljs https://github.com/nathants/aws-gocljs