Next.js and Remix's focus on SSR has added cruft and complexity to the core React use case of building interactive apps. @tanstack.com is the antidote to this: an opinionated framework that actually helps you get stuff done rather than forcing you to optimise for someone else's e-commerce use case.
Reposted from
Tanner Linsley
For a long time I slightly resented Gatsby for the added pressure it gave me to stop building React Static, but I miss it now. The React ecosystem is overflowing with homogenous thinking lately and Gatsby’s decline didn’t help that.
🫡 Gatsby and @kyle.bricolage.io
🫡 Gatsby and @kyle.bricolage.io
Comments
- Way better TS support. Way.
- Much needed URL state management APIs
- Built-in caching for the whole router
- And yes... integration with Query, but let's not inflate having a pluggable API design to more than it should be.
- Optional segments missing in TSR
- I know how to cache and how to use loaders and actions so nothing special there.
- Yes RR has less hand holding but I don't find that to be a bad thing
- TSR is too beta for my taste