I'm probably going to end up jumping through SO many hoops and challenges to support server components in TanStack Router, Bling and Start and at least for the time being, I resent the distraction. I'm constantly reminded in my interactions with our users and customers that it likely won't move the needle, neither for them or our devs. That said, the technical prowess we're seeing to make server components work is truly amazing and the technical implications it will have on some use-cases are very, very exciting. I'm sure it will foster plenty of innovation for the challenges it's aimed at. Here on the bleeding edge of thought-leadership (twitter) it's all too easy to forget that your users are just a deploy away though and that it usually doesn't require massive paradigm shifts or rewrites to 🚢 things that will make them smile. From where I'm standing nothing has been more game-changing for me (and sometimes my users) over the last few years than: - robust server-state caching/management (@tan_stack Query) - type-safe client-server communication (@bufbuild, @trpcio) - @tailwindcss (move along haters, nothing to see here) And going forward, the things that get me even more excited: - Type-safe Routing (TanStack Router) - Client-Server RPCs, inline bundle-splitting (Bling) - Type-Safe forms (maybe not new for you, but for me) - Scalable data visualization (@observablehq Plot) Take a break from the chatter (yes, it's exciting) and remember to focus on what *your* users need.
@tannerlinsley Don’t forget @blitz_js, the OG typesafe RPC still going strong 😎
@flybayer @tannerlinsley @blitz_js I love the @blitz_js RPC API so much.