the intention is to say: "we need more info"

all this works today, mind you, its just behind an experimental flag

I'm good without caveats at the moment 🙂

it is always safe to say "result == has_permission"

if we're not sure, that won't match

cool

gotta say, you guys using grpc has been pretty awesome for me since I'm using rust. Generating a clients and then condensing them into a single, more client was a breeze.

and buf has come a long way; their doc generation is great.

anyway, /offtopic

glad to hear!

yeah, buf is super nice

yea, they are really pushing grpc/protobuf. they just took over grpc-validate

supposedly typescript/javascript is the first language they'll be adding which will pair really well with their connect-web.

TS/JS needs a lot of love when it comes to proto

and I say that as the guy who wrote the first compiled JS lib for Proto

yea it does.

that's awesome!

I'm not really sure why clientside grpc hasn't adopted more tbh

the need for translation

handling binary data client side was quite difficult until recently

and performance of doing binary decoding was... poor, at best

so everyone did JSON for a while, which was faster but had its own issues

right, and in a lot of cases that meant adding a bridge

yep

still though; the bridged approach still seems more appealing than, say, graphql

as with all things, its very context sensitive

true

I see the appeal of GraphQL for certain types of apps

it seems pretty suited for graph intensive applications but the craze of replacing all rest APIs with it made no sense to me. dgraph, which used a modified graphql as a graph db query language, seemed incredibly interesting to me.

yeah, its a fascinating domain