Why We Ditched GraphQL for TRPC

#1

Post by mcavaliere » Mon, Nov 14, 2022, 6:19 PM UTC

Why We Ditched GraphQL for TRPC
echobind.com

Re: Why We Ditched GraphQL for TRPC

#2

Post by mcavaliere » Mon, Nov 14, 2022, 6:19 PM UTC

In our Next.js boilerplate, we got some nice gains and DX improvements from replacing our Apollo Server installation with tRPC.

Re: Why We Ditched GraphQL for TRPC

#3

Post by brodouevencode » Mon, Nov 14, 2022, 6:32 PM UTC

mcavaliere wrote: post #2

In our Next.js boilerplate, we got some nice gains and DX improvements from replacing our Apollo Server installation with tRPC.

I'm sure, but it requires your entire stack to be TypeScript. My clients want to be language agnostic, which requires me to be.

Re: Why We Ditched GraphQL for TRPC

#4

Post by mcavaliere » Mon, Nov 14, 2022, 8:57 PM UTC

brodouevencode wrote: post #3

mcavaliere wrote: post #2

In our Next.js boilerplate, we got some nice gains and DX improvements from replacing our Apollo Server installation with tRPC.

I'm sure, but it requires your entire stack to be TypeScript. My clients want to be language agnostic, which requires me to be.

That makes sense. Our boilerplate is for all new-code projects where we get to pick the stack, in which case we default to all things TypeScript anyway. If a client project has an incompatible existing codebase, we take a different approach.