Content
@
0 reply
0 recast
0 reaction
Darryl Yeo đ ïž
@darrylyeo
Svelteâs ecosystem is huge because itâs trivial to adapt vanilla JavaScript things. (Itâs about to become even easier when Svelte 5 drops this April!) In React, everything has to be wrapped or rewritten in terms of React providers and hooks â itâs practically a different programming language.
5 replies
0 recast
10 reactions
typeof.eth đ”
@typeof.eth
Ugh, I don't wanna be the guy that is just constantly defending React (it's not that great, tbh), but _everything_? I'm using vanilla viem in a React project. Plus all the other go-to libs like lodash, zod, etc. > itâs practically a different programming language React has a learning curve, but it's really just JS.
2 replies
0 recast
1 reaction
Darryl Yeo đ ïž
@darrylyeo
Fair â I should clarify I mean âeverythingâ that gets consumed at the component level. At some point or another, any JavaScript reference used for component state has to be adapted to follow the laws of React hooks. Everything up until that point or outside the component realm is indeed just vanilla JS đ
2 replies
0 recast
0 reaction
typeof.eth đ”
@typeof.eth
We just went from implying you can't use vanilla JS libs in React and that it's so different from anything else that it's basically not JS, to: If you need to use the state hook, you have to use hooks. React's state management and lifecycle method handling is not as good as other frameworks. You could just say that.
1 reply
0 recast
1 reaction
Darryl Yeo đ ïž
@darrylyeo
Yup agreed, âeverythingâ was a poor word choice on my part â my bad. Wasnât implying that you couldnât use vanilla JS libs in React â rather that the added friction of adapting vanilla things to React hooks makes the React ecosystem feel closed off and distinct from the vanilla ecosystem.
0 reply
0 recast
1 reaction
