←back to thread

Using gRPC for (local) inter-process communication (2021)

(www.mpi-hd.mpg.de)
83 points zardinality | 3 comments | 20 Nov 24 13:42 UTC | HN request time: 0.681s | source
Show context
pengaru ◴[20 Nov 24 16:34 UTC] No.42195597[source]▶
There's a mountain of grpc-centric python code at $dayjob and it's been miserable to live with. Maybe it's less awful in c/c++, or at least confers some decent performance there. In python it's hot garbage.
replies(5): >>42195747 #>>42196231 #>>42196568 #>>42196845 #>>42197041 #
1. seanw444 ◴[20 Nov 24 18:37 UTC] No.42196845[source]▶
I'm using it for a small-to-medium sized project, and the generated files aren't too bad to work with at that scale. The actual generation of the files is very awful for Python specifically, though, and I've had to write a script to bandaid fix them after they're generated. An issue has been open for this for years on the protobuf compiler repo, and it's basically a "wontfix" as Google doesn't need it fixed for their internal use. Which is... fine I guess.

The Go part I'm building has been much more solid in contrast.

replies(1): >>42197996 #
2. lima ◴[20 Nov 24 20:53 UTC] No.42197996[source]▶
I guess you're talking about the relative vs. absolute import paths?

This solves it: https://github.com/cpcloud/protoletariat

replies(1): >>42198057 #
3. seanw444 ◴[20 Nov 24 20:59 UTC] No.42198057[source]▶
Yeah, my script works perfectly fine though, without pulling in another dependency. The point is that this shouldn't be necessary. It feels wrong.