3 ms·
I think well designed safety critical bare-metal stuff and well designed browsers have a difference in complexity placement - within bare-metal work you need to
by munk-a 7y ago
I think well designed safety critical bare-metal stuff and well designed browsers have a difference in complexity placement - within bare-metal work you need to be aware of and account for the full domain range of values any systems you talk to can produce (including error output) and account for those - while browsers[1] tend to be more emergently complex with relatively secure and safe input but a lot of complexity in how those inputs are handled.
One system is taking a complex world and trying to reduce it to a safe and simple system - the other is taking something safe (some rando user inputs and a pile of HTML) and turning it into something complex - a rendered website.
Granted, I think value domain identification is one of the only ways for complex software to at all survive growing into a legacy system - so maybe the core difference is the nice stress free life of a system where the worst outcome of a critical failure is someone not being able to post on facebook ;P
1. Lets ignore firefox and JS and just assume we're in the 90's downloading HTML sites...