dagar
I haven't had a chance to try it yet, but in theory I like the idea of something like Zenoh Flow to describe the larger data flow graph. https://zenoh.io/blog/2023-02-10-zenoh-flow/
> But I always like to say, why spend 5ns calling a function when you could spend 1ms waiting for a context switch or 50ms for the next event loop to tick over?
I think your context switch timing is off by several orders of magnitude, but regardless these things aren't one extreme or the other. For sharing data across threads, to an external system, or logging and visualization I still like pub/sub (and I've seen more than my share of horrible abuse), but it definitely shouldn't be treated as one size fits all.
Annoyingly in a lot of real world setups you can't have these guarantees. Your gyroscope, camera, etc are all producing data asynchronously often with slightly different clocks, and they all have different little idiosyncrasies and failure modes.
For example the Mars helicopter almost crashed because it missed a single frame. https://mars.nasa.gov/technology/helicopter/status/305/survi... If possible you absolutely want to fix the frame drop in the first place, but your algorithm should also be able to handle the drop out (or at least reset/recover).
This is how I've structured a control system, but using a pub/sub system to share data across those boundaries (and log/inspect in general). "Nodes" that share some resource or fundamentally run back to back based on the data flow can live in the same thread. Higher rate components (eg inner loop controller) live in a thread with a much higher priority. All of this is event driven, deterministic, and testable.
If you have more details about the system you're imagining I'd love to learn more, because so far I don't see what's incompatible with what you've described.
http://shop.lenovo.com/us/en/laptops/thinkpad/x-series/x1-ca...
I haven't been able to find libraries that can handle the full 165888x65536 10 gigapixel image.
http://www.displaywars.com/4,65-inch-16x9-vs-7-inch-16x10 http://www.displaywars.com/4-inch-16x9-vs-7-inch-16x10
Nicely done!
I believe the 3.6 lbs you mentioned is with the 9 cell 15 hour battery.
For comparison the 11" and 13" Macbook Airs are rated 5 and 7 hours, respectively.
Doesn't my android phone already do this?
-fastcheck
do fast (and slightly unsafe) update detection on windows