3 ms·
Containerisation already goes a way towards this, each executable is bundled with what it needs and nothing else. And the next step is one app per hardware, whe
by JulianMorrison 5y ago
Containerisation already goes a way towards this, each executable is bundled with what it needs and nothing else. And the next step is one app per hardware, where you have maybe a minimal stripped OS that just launches your app, effectively a container in hardware. I think Google does this a fair amount.
The jump from this to RTOS is large, though. The abstractions are different. The limitations are different. You probably need to rewrite anything you need. And what do you gain? Mostly only predictable latency, and the ability to run on very limited (but cheap) hardware. Which you need why?
- gmueckl 5y agoAlso, massively reduced energy consumption if you choose the right hardware (e.g. ultra low power microcontrollers).
- JulianMorrison 5y agoYou can get a lot of the way towards that without needing a RTOS though.
- kevin_thibedeau 5y ago> Which you need why? If I'm selling a million Tamagotchis I'd rather use the 5 cent part over the 50 cent one and pocket the extra $.45M. A $5 part is a nonstarter.
- littlestymaar 5y ago> Containerisation already goes a way towards this, each executable is bundled with what it needs and nothing else. Maybe in theory, but in practice most people still ship an entire OS in their containers (most of the time it's Alpine and it's not to big of a deal, but too many times it's an entire Debian!)