News for hackers. Stuff that matters.

A comment on Oxide on My Wrist: Hubris on PineTime was the best worst idea. Parent comment

Re:Oxide on My Wrist: Hubris on PineTime was the best worst ... by zozbot234 on Monday March 28, 2022 @11:30AM (#30831560)
> Rust helps, but isnt immune (e.g. stack overflows).

This is a good point but isn't Hubris designed to use statically bounded amounts of memory anyway, like much embedded software? AIUI, this was a key reason for keeping their design focused on synchronized requests, avoiding the hard-to-predict buffering that's needed for supporting 'async' models.

[ Parent | on HN ]
Re:Oxide on My Wrist: Hubris on PineTime was the best worst ... by steveklabnik on Monday March 28, 2022 @01:06PM (#30832773)
Defense in depth matters. The blog post shows an example of Hubris correctly killing a task that's touching memory it's not supposed to. That "supposed to" was due to a configuration error, but configuration errors can and do happen, and maybe would not be as benign as this one was.
[ Parent | on HN ]