grpc is lightweight, pretty fast, more universally supported than capn proto for other languages including javascript! and and gRPC's default transport is QUIC which is a UDP based replacement for TCP which aims at fixing "head of line" contention

if there is any candidate for an augmentation to nostr protocol it's gotta be grpc/protobuf

protobuf is the encoding, grpc is the protocol, it handles the request/response flow

Reply to this note

Please Login to reply.

Discussion

If the use for a second protocol is non-browser non-JavaScript non-JSON then there is no need to support JavaScript. If the goal is to fully replace WebSockets/JSON, then yes, it would need to be something with wide support such as gRPC.