Convert custom message format code to something more reasonable #8

Closed
opened 2025-01-10 20:15:51 -05:00 by imterah · 2 comments
Owner

Summary

The bulk of code that's hard to read is in backend/commonbackend. This code has led to some hard-to-catch bugs sneaking in, also. It's also less modular and portable.

Perhaps we should move to Protobufs?

# Summary The bulk of code that's hard to read is in `backend/commonbackend`. This code has led to some hard-to-catch bugs sneaking in, also. It's also less modular and portable. Perhaps we should move to Protobufs?
Author
Owner

Further consideration has me thinking that we should use Cap'n Proto instead.

It has less annoying data types, and it's apparently faster.

Further consideration has me thinking that we should use [Cap'n Proto](https://capnproto.org/language.html) instead. It has less annoying data types, and it's apparently faster.
Author
Owner

It would be too much work for virtually nearly no benefit other than better cross-language compatibility.

It would be too much work for virtually nearly no benefit other than better cross-language compatibility.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: imterah/hermes#8
No description provided.