Sidebar: There's a Python fbink module, no need to spawn the CLI tool. (fork is expensive).
In this context, you're already fork'ing for lipc anyway, so, eeeeh.
Still, ought to be mentioned
.
@mergen3107: Python/bash is unlikely to be much of an issue here. It's going to be expensive to spawn (more so for Python), but that's it. I'm assuming this *isn't* spawned every time, but instead spawned only once (i.e., a daemon).
Once that's out of the way, Python is actually likely to be less awful than bash, because bash isn't even bash here, but an old and ugly busybox ash
.
That said, nothing computationally expensive is really tied to the language here, as far as the internal logic goes.
If you *do* need to spawn stuff often, you've kind of already lost before even starting, so, back to the design phase
.
----
In which case: that leaves you basically C (and/or LuaJIT). There's an open basic header for using lipc in C, f.g. (c.f.,
https://github.com/yparitcher/kindle-zmanim for a recent example).