Frontend

Idk what's worse, 15 useStates in the root of an app or this many useEffect dependencies 😭

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)

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

I still don’t understand why VDOM. Solid, Knockout, S.js nailed it years ago

A brief history of JavaScript frameworks, ranked by client-side rendering performance 🧵

https://youtu.be/E5amN0_1XyE

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.

Based House. Engineering @neynar. Amusement, wonder, and uncertainty ✴︎ libred.org

Florence, Metropolitan City of Florence, Italy

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

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.

i imagine it’s the ecosystem people are choosing, not necessarily the framework itself