Post

James Arthur
@thruflo.com

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.

Tanner Linsley@tannerlinsley.com

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

Tanner Linsley
@tannerlinsley.com

Your comment is telling that you've likely never actually tried TSR. - 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.

0 reposts0 likes

Pablo Mayobre
@pablomayobre.bsky.social

Love what you all are doing with TSR and TS Start, I just prefer the stability and ecosystem RR built over the last 5 years. TSR is getting very close to that tipping point where it can make me question my decisions but it will not be easy

Pablo Mayobre
@pablomayobre.bsky.social

- TS Support is fine in both nowadays - 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