3 ms·

I’m already seeing articles about people ditching GraphQL and going with tRPC.

• emptysea 4y ago
  Only catch really is you need to have a typescript backend I'm looking forward to more tRPC style things that can integrate across language boundaries. I'm okay with some simple codegen to support it
  • easrng 4y ago
    tRPC doesn't actually need typescript, you can use it with normal javascript just fine.
• helsontaveras18 4y ago
  I've just started with tRPC and for internal dashboards, there's definitely no going back. The speed of development is unmatched. Not having to do any codegen is mind blowing.
• omani 4y ago
  I was excited to hear about tRPC until I realized that there seems to be the need for a monorepo. can't just keep the backend and let clients talk to me.
  • easrng 4y ago
    you don't need a monorepo, you just need to be able to import the types, they don't need to be in the same package.
• kyriakos 4y ago
  Is trpc a javascript only protocol?
  • astonex 4y ago
    The t in trpc is for typescript
    • kyriakos 4y ago
      Still targeting nodejs backends then.
• speedgoose 4y ago
  These people only use JavaScript and TypeScript? Being restricted to one programming language is a huge difference compared to rest, GraphQL, soap, grpc, CORBA… It sounds a bit like Java RMI, something that cannot succeed.