3 ms·
What? There's no reason but product level features to choose an RTOS. An RTOS won't be more ergonomic, won't make life easier in general, won't give you any new
by BoorishBears 3y ago
What? There's no reason but product level features to choose an RTOS. An RTOS won't be more ergonomic, won't make life easier in general, won't give you any new primitives that are development related...
You choose it because the product demands good performance, low latency, etc. And the Rabbit fits that bill pretty cleanly.
Closer to bare metal doesn't mean it needed to be running a custom GPU driver, but it's also not running a Flutter/Compose app on a 6 year old GPU core...
- AlotOfReading 3y agoTypo, didn't realize I wrote "RTOS" out of habit instead of "OS". Regardless, I wouldn't consider those product level features and I also wouldn't consider them strictly limited to RTOSes either. A normal operating system is going to be significantly better for performance on good hardware, which is why all of the top supercomputers are running a variant of Linux. An RTOS may give you lower latency, but it's really specialized to realtime as I'm certain you're aware. You choose an RTOS because you either have those realtime constraints, you want a "smaller" system, or you're running hardware that can't support a full-fat operating system (e.g. ESP32) and the RTOS offerings are what's most convenient. I don't think any of those apply to the Rabbit device in a realistic way. Implementing it in an RTOS wouldn't speed up the server-side inference that's doing the actual work here, for example. Since there aren't reasons to go with an RTOS, your criteria for OS selection are going to lean towards the meaningful benefits a normal OS like Android offers, both in terms of development tooling and board support.