Upkie
Why weakly-typed IPC rather than Python–C++ bindings? #395
stephane-caron
started this conversation in
General
Replies: 1 comment
-
|
Upkie's software is designed for prototyping: it strives to eliminate intermediaries when it can, and keep a low barrier of entry. Python bindings bring the benefits of typing and are a good choice in many production contexts, but like interface description languages, they add overhead in terms of learning, bookkeeping code and compilation time. In this software we rather go for a crash-early approach: fast changes, fast blunders (interface errors raise exceptions that end execution), hopefully prompting fast fixes (know immediately when an error was introduced). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The inter-process communication between agent and spine by serializing dictionaries has drawbacks, for instance it is weakly typed. Why choose this rather than, for instance, Python–C++ bindings?
Beta Was this translation helpful? Give feedback.
All reactions