Content
@
0 reply
0 recast
0 reaction
Darryl Yeo đ ïž (at Devcon)
@darrylyeo
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.
3 replies
3 recasts
24 reactions
Darryl Yeo đ ïž (at Devcon)
@darrylyeo
I like how as of Svelte 5, all rune-based reactivity outside of components must be contained within `.svelte.js` / `.svelte.ts` files. This lets you explicitly mark that something is written for a Svelte-based runtime while keeping compatibility with JavaScript import tooling. Would love to see this become a trend. https://svelte.dev/docs/svelte/svelte-js-files
0 reply
0 recast
5 reactions
Marc BHE Season đâŁïž
@bighamenergy.eth
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/
1 reply
0 recast
2 reactions
henrywifđ”
@hz
Hooks was the best thing and worse thing that ever happened to React. Thanks to hooks React is super powerful. Unfortunately, 95% of React apps in the wild a riddled with technical debt đ€ź.
0 reply
0 recast
1 reaction