Content
@
0 reply
0 recast
0 reaction
Darryl Yeo đ ïž
@darrylyeo
The year is 2025 and React devs are still stuck in a local maximum with this archaic syntax and absolute footgun of a dependency management abstraction Imagine all the keystrokes, CPU cycles and brain cycles we collectively could have avoided over the last decade if the industry just moved on from virtual DOM frameworks instead of blindly following runaway network effects (pun intended)
3 replies
3 recasts
11 reactions
Rafi
@rafi
I still donât understand why VDOM. Solid, Knockout, S.js nailed it years ago
1 reply
0 recast
1 reaction
Darryl Yeo đ ïž
@darrylyeo
Iâm half-convinced React culture is a cult. People who are deep in it just don't bother to try the alternatives or question the fundamentals. https://warpcast.com/darrylyeo/0x89943d9c
1 reply
0 recast
1 reaction
Barbs
@bbq
i imagine itâs the ecosystem people are choosing, not necessarily the framework itself
1 reply
0 recast
1 reaction
Darryl Yeo đ ïž
@darrylyeo
A framework donât necessarily need a big ecosystem â as long as it plays nice with web standards, you have everything you need to create a great experience. When an ecosystem grows too big it can actually be a sign of fragmentation and library churn.
1 reply
0 recast
1 reaction
Barbs
@bbq
true - people just get used to their toys and itâs hard to pry them away. sometimes the ecosystem is just lacking though, im a big fan of svelte but react is still my default for web3 as nothing comes close to wagmi hooks from a dx perspective
1 reply
0 recast
1 reaction
Darryl Yeo đ ïž
@darrylyeo
You're gonna like this pull request then! https://github.com/wevm/wagmi/pull/4365
1 reply
0 recast
2 reactions
Barbs
@bbq
damn this would be huge, ill be watching this closely - thank you we had a stab at a similar thing in the past, but the space moves so quick its hard to keep pace with the various updates https://github.com/sveeeth/sveeeth
1 reply
1 recast
1 reaction
