> 1. Does the Blitz RPC thing work the same way as TRPC?

Depends what you mean by "same way". Yes in that both provide fully typesafe client-server communication. No in that the Blitz implementation is a tiny fraction of the size and does not have any Typescript-related performance slowdown at scale like TRPC.

The Blitz RPC tech itself will scale forever. However as a company scales it'll probably face another problem which is API contracts between internal teams. When you hit that, you may want to adopt GraphQL.

> 2. Having got used to Vite I just cannot go back to Webpack (which IIRC Next still wraps).

Yep, I want Next.js to get off webpack too

I'd strongly suggest having a direct comparison vs. tRPC page in the documentation. I doubt we're alone in being curious, and this is the real flagship feature.

Since you say Blitz is no longer tied to Next - does that mean it can be used with Vite? Again I doubt I am alone in thinking this would be huge.

I've said it in other comments but to repeat - I think this is super interesting.

Honestly I can't decide whether this is a framework or a feature. But it's definitely interesting.

> I'd strongly suggest having a direct comparison vs. tRPC page in the documentation

Yes, it's coming.

> does that mean it can be used with Vite?

Yes, but we do have a bit more work to clean up our internal package dependencies and APIs so that this works.

It won't scale forever. You'll need project references in the same way as we need in tRPC on large projects.

Unless I'm missing something, Blitz RPC add's zero TS overhead. So the limitation will be the total amount of TS code you have which is not related to Blitz.

I’ve never used TRPC but curious to learn more about the slowdown. Is that a slowdown with Typescript or a runtime thing?

By their own admission (or at least those of their advocates who I've paid attention to) tRPC isn't suitable for large projects.

tRPC as I understand it basically serves definition files to the client using a clever misuse of Typescript - but over time that means Typescript has to conditionally evaluate every type in your app to find the correct one. Or something like that.

My understanding of BlitzRPC from their documentation is it's more Svelte-like with the "everything is a magic compiler" philosophy. This may come with issues but it sounds pretty nice.

> with the "everything is a magic compiler" philosophy

Blitz RPC has 1 minimal magic step, which is a webpack step to replace the resolver imports in client code with a fetch function and to add resolvers to the server-side API endpoint.

And we'll be adding an API that lets you use Blitz RPC without webpack or any compile step.

The slowdown occurs in the editor (red squiggles, autocomplete, etc.). tRPC relies heavily on TS inference, which the TS team strongly discourage due to performance concerns.

Slowdown with Typescript and IDE completion. Not runtime.