Frontend

nothing is more disappointing than a library providing only react support.

"nobody has time to make versions for each framework!"

not what we are asking and not what you should do even if you're able to. Just make a vanilla JS version and a react version.

This ends up being better for your library long term

Treat React Hooks for what it is – a separate programming language.

Hooks happen to use JavaScript-y syntax and package mechanisms, but they ignore all the usual conventions around references and closures due to the implied re-rendering loop and are thus incompatible with the rest of the JavaScript ecosystem.

Since I adopted zustand hooks are gone forever, it even allows me to work in a Vanilla style if i want, state management and interactions are pretty easy now, just sharing in case it's useful to not get so entangled with react

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo

Chiang Mai, Mueang Chiang Mai District, Chiang Mai, Thailand

Since I adopted zustand hooks are gone forever, it even allows me to work in a Vanilla style if i want, state management and interactions are pretty easy now, just sharing in case it's useful to not get so entangled with react

https://zustand-demo.pmnd.rs/

Barcelona based developer. I enjoy comics gaming and sci-fi

Have you used Zustand outside of a React project before? Curious what that experience is like.

Hope it’s not the same experience as using it in React 🤧

I am using it on react. Use case here https://app.unionavatars.com the whole application uses react zustand and drei

eng @matchaxyz 🍵 • @0xproject • casting in /chiblings • /matcha • /accessibility • /henry-dev • /investooor