News for hackers. Stuff that matters.
Re:gRPC: The Bad Parts by throwaway894345 on Thursday June 27, 2024 @02:54PM (#40813764)
Ignoring the incompatibilities in word size, endianness, etc, how does a Go or JavaScript or etc program on the receiving end know what `mystruct` is? What if you want to send string, list, map, etc data?
Re:gRPC: The Bad Parts by anon291 on Friday June 28, 2024 @10:06AM (#40820732)
string, list, map, etc? You have to use an encoding scheme.

As for go / javascript? I think most languages have the ability to inspect a raw buffer.

Re:gRPC: The Bad Parts by throwaway894345 on Friday June 28, 2024 @10:34AM (#40820987)
> string, list, map, etc? You have to use an encoding scheme.

Yes, you have to use an encoding scheme like JSON or Protobufs. Dumping memory directly down the pipe as you're suggesting doesn't work.

> As for go / javascript? I think most languages have the ability to inspect a raw buffer.

No language has the ability to read a raw buffer and know what the contents are supposed to mean. There needs to be a protocol for decoding the data, for example JSON or Protobufs.