Don't Migrate To tRPC

Taylor Brian Brown Sharon Rodriguez Mary

I just subscribed

The content is good, the title is horrible.

TLDR: trpc is addictive, it has a very strong inhibitory response.

The only reason im using typescript is for frontend other than that i hate js/typescript

I love this video❤

Spot on! Watched this at 9 AM, coded non-stop until 3:15 AM, and now my project's transformed from REST to tRPC.

Is this still relevant or can I ignore? Considering t3 stack is in love w trpc.

Which cms I can use in t3 stack?

Not sure about other languages or frameworks, but no one I've talked to that uses Ruby on Rails would feel this way. tRPC is much harder to use than Rails. Here are lots of reasons why; be aware the scale or my perspective is very large projects not Google size, but Medium Enterprise CRM size.

Ok here is why:
1. tRPC's nested routing and routing in general. The structure isn't noisy and hard to discern. This is an area that needs to be memorized-ish on any project since the names are not always so obvious. It's just delay and cognitive load. I spend zero time in Rails on this problem. People will say "Roger, but you have a single file with all the routes and it's noisey". That's true, but due to conventions I open and file and can immediately without thought find what I need anywhere in the file and that's on bad projects done by weak devs.

2. Testing! Postman nor any other tool like that makes little to no sense, since setting up any routes is massively time consuming and wlll often run afoul of some procedure. It's hard graft just to do something that any RESTful API can do in 5-10 seconds. In development cognitive load is a huge cost on development.

3. Bug fixing: So you are clicking a button and you don't see a route or anything. No console log? Oh well. You are lucky if the developer created any kind of URL that will even hint at where that call is being responded to within your procedures and where it is based on a button click. This is one of the worst aspects of tRPC.

I'm tired of griping, so I'll stop, but honestly if you are a nodeland user and haven't tried anything outside that ecosystem, then learn Rails and you'll see what I see.

Also I really don't know why people think Typesafe code is such a huge thing; Github and many other large critical applications are written in Ruby which isn't typesafe. Typesafe is a nice to have, but good tests, that are easy to write and easy to reason about are more valuable.

Is frontend and backend written in TS? Yes? use tRPC, else don't. Simple.

Theo 사랑해💚

That's what I thought. tRPC is useless if you are not using the same repo for both your FE and BE and if you are not using Typescript. Add It forces you to use React-Query. WTF!

@t3dotgg can you tell me that if I have a standalone next js application why do I need trpc, i'm asking this because the real benefit of using trpc is that you can have better client-server communication but with using getServersideProp and other similar function we can do the same. And the trpc endpoint can't be treated as rest endpoints. So lets say in your ping app what is the significance of using it instead of something like getServersideProp ?

is there a crrate-t3 app for nuxtjs? i actually love using trpc once i tried it with zod, and i wanted to use it in our nuxtjs project. im not much of a nextjs user, but i really love the idea of trpc into monorepos

So the moral of the story is (LIKE NEARLY EVERY TOOL) don't use it until OR unless you have to. This video doesn't just pertain to tRPC. It pretty much covers nearly EVERY framework, tools for DX, edge function providers, cloud hosting solutions, bundling, performance enhancements and logging / monitoring choices. This video has the right messaging but could have literally been a tweet. Like the one where you said "The amount that tRPC has improved the quality of our code, the speed of our delivery, and the happiness of our devs is hard to comprehend. I know I shill it a lot but seriously, please try @trpcio"

does trpc work with golang

It is possible to hace the client tRPC on a React app running on a Kubernetes pod and the server tRPC on a BFF running on another pod?

but if it lets me migrate off of useSWR I should definitely migrate the one Page that's done before starting the next one I just started writing the SSG for, right? :)

I like what I see from tRPC but I'm currently not using a monorepo. The code reusablitiy from the monorepo also looks attractive to me. What are your thoughts on moving from distributed repos (some for multiple different front ends and microservices backends) to a monorepo?

i write my backend in rust, so no trpc

I think the question that's getting dodged is whether or not tRPC will become obsolete if RSC / Next 13 becomes the meta for full stack app development. I have played around with the t3 stack and I love the ergonomics of tRPC, but I also love the ergonomics of Remix and the Next 13 app directory. What is the optimal path for full stack apps and DX? Am looking forward to seeing how things shake out!

not gonna lie, You are getting better at writing eye-catching titles. 😂

Hey guys you think it's a jump of concepts learn trpc befor learning graphQL?

"Chance's R..." is a great country western club. tRPC is great if you can make the rest of your org happy.

just do a full rewrite.

Please make a video of how to implement trpc with the next 13 app folder 🙏

Why don't we talk about module federation?

Have you looked at gRPC? Support across many languages!

Another great video as always.

Guys, I am looking for a job that uses T3 stack.
Any recommendations on where to look?

Thanks in advance

What's ya'll's opinion on the usage of tRPC in a non-monorepo context (i.e. via publishing a private package)?

How did you approach real-time chat in trpc?
Websockets or polling?

i literally decided to learn trpc today 💀💀

What's the way to add rest to it? Like integrating an existing API.

One ergonomic benefit of tRPC that I've not seen many people praise is the component level SSR data fetching story.

I've migrated my large REST API over to tRPC because of the end-to-end type safety, client code generation, and better developer experience. However, I still have kept some traditional REST endpoints around for non-JSON data purposes, such as file uploads and XML responses (RSS feed). tRPC doesn't solve every problem but it solves 99% of them and I absolutely love it.

Doing the migration, however, I kept a lot of RESTful API design implementation around so that my frontends can keep working as-is (just swapping in trpc/client) with the same data model and structure. My next step is to rethink the "endpoint" (function) designs to better align with this new world and not be coupled to RESTful standards.

I use both trpc and normal queries due to an app we use, it's at least 5 times better when I want to implement something from tRPC comparing with vanilla node queries

this is a cute bag but i would never wear this no i would not

Your hair is amazing!

Honestly great advice.

I'm just starting to use TRPc and it was a bit of a ramp up initially, if I had gone in trying to migrate everything it might have become a blocker. I'm now using it though and can't see going back to REST anytime soon.

can you do a video explaining the server$() function in solid start compared to the functionality of tRPC?

While the trpc may be super great dev experience, you are basically locking yourself to typescript only for backend and frontend. Thus making any future migration to different backend technology very costly. Since you cant just reimplement one backend endpoint at a time using different tech.

I'm literally gunna u sub bc you always try to guilt trip us into subbing and liking lol. The good vids will get recommended to me by the alg anyways

Subbed to learn so thank you dude 😎

Hey @elonmusk --- learn how to speak like this dude.....we have more respect for him and his wisdom than your Ill funds ya phreakazoid

Can tRPC Endpoints be externally consumed (outside of the Next.js App) for e.g. a Python script?

This is the way Theo! Sub 4 mins video with no BS, don't get me wrong I really appreciate your content but my time is precious and limited.

He's just talking nonsense :)

this dude changes like the tailwind