Not to take away from your explanation, but this is actually the key point that a lot of developers have been fighting in the last couple of years.
We've "had" end-to-end typesafety with codegen tools openapi/swagger and graphql etc.
However, the big issue with a lot of those tools is that you end up having to manage this compile step.
The real magic of trpc is exactly this point about it being without a compiler, where the types are derived from the very same typescript files - this is what gives it this immediacy and feeling of it being instant and not having to deal with a compile step.
I've always wondered whether we'd get the same benefits and niceties with a really streamlined compiling approach - perhaps something like phero. But it's just a little harder of a sell compared to the built-in typesafety you get from trpc
We've "had" end-to-end typesafety with codegen tools openapi/swagger and graphql etc.
However, the big issue with a lot of those tools is that you end up having to manage this compile step.
The real magic of trpc is exactly this point about it being without a compiler, where the types are derived from the very same typescript files - this is what gives it this immediacy and feeling of it being instant and not having to deal with a compile step.
I've always wondered whether we'd get the same benefits and niceties with a really streamlined compiling approach - perhaps something like phero. But it's just a little harder of a sell compared to the built-in typesafety you get from trpc