🗣️ Pronouncing tRPC: A Case for "Typed Rung Peg Call"

[psychoslave]

Hey tRPC community! 👋

I’ve been thinking about alternative way to pronounce tRPC. I’m not fond of abbreviations to start with. Especially when they are semantically opaque and vowel-only acronyms. So I thought, without getting rid of the commodity of the shortness, could we do better than "tee-are-pee-see"? So, I reflected about a more intuitive alternative and came with "Typed Rung Peg Call" (/taɪpt rʌŋ pɛɡ kɔːl/).

Why this works:

• Typed → Directly ties to TypeScript.
• Rung → Evokes a step or connection (like climbing a ladder to bridge a gap, hinting at "remote").
• Peg → A simple, neutral anchor (like a placeholder or hook for your procedures), and also compare with the journalistic definition: a topic of interest, such as an ongoing event or an anniversary, around which various features can be developed.
• Call → The action of invoking a procedure (already a perfect fit).

Benefits:

✅ Just as short: still 4 syllables, as "tee-are-pee-see."

✅ More meaningful: Hints at the purpose of tRPC, even for newcomers.

✅ Easy to remember: Flows naturally in conversation.

Example in the wild:

"We’re using tRPC—Typed Rung Peg Call—to handle our API layer."

Why not just stick with "tee-are-pee-see"?

• It’s opaque: Doesn’t convey anything about the library’s purpose.
• It’s not shorter: Doesn’t provide any time benefit when pronounced that way.

Your turn!

What do you think? Could this catch on? Or is there an even better way to pronounce tRPC? Let’s discuss!