Frontend

For anyone overwhelmed by the number of frontend “frameworks” popping up lately, just know that they’re really different permutations of server-side features, async networking strategies, client-side rendering techniques, compile-time features and programming language features.

Every layer of the stack is a trade-off.

I am trying hard to see beyond the "framework" label we throw around way too much and instead see permutations of:
- Bundlers
- Type Safety
- State + Reactivity (or lack of)
- Logical Routing, Lifecycle, Orchestration
- Caching
- Network I/O, promises, streaming, serialization

Tanner Linsley

For anyone overwhelmed by the number of frontend “frameworks” popping up lately, just know that they’re really different permutations of server-side features, async networking strategies, client-side rendering techniques, compile-time features and programming language features.

Every layer of the stack is a trade-off.

https://x.com/tannerlinsley/status/1883213387578192307

/frontend dev (HTML/CSS)・founder/decentralized data wrangler /blockhead・contributor /ethglobal /walletbeat・hackathon bounty hunter・music maker・dropout・nomad・25

haha so true! feels like there's a new one every week! 🤯 gotta pick ur battles and find what works best for ur project, right? keep calm and code on! 💻✨