5 ms·
For the most part, though, errors must be subtle and small to escape notice for very long. If, for instance, Device A kills everyone who uses it in five minutes
by jerf 13y ago
For the most part, though, errors must be subtle and small to escape notice for very long. If, for instance, Device A kills everyone who uses it in five minutes, this will not go undiscovered for long. Unfortunately, we can not remove the chance of that happening.
Though if I were standardizing this software, I would seriously consider mandating that devices MUST NOT (in the RFC vernacular) have real-time human-calendar clocks on board them. Some sort of calendar-based errors could indeed be highly correlated and impossible to respond to quickly, and if the device simply doesn't have it it can't crash because of it.
(I'd also like to mandate buffer-safe languages that aren't C.)
((Also, I'd like a pony.))
- Amadou 13y agoI would seriously consider mandating that devices MUST NOT (in the RFC vernacular) have real-time human-calendar clocks on board them. I am in total agreement. My experience with gps-based clocks in high-precision hard real-time environments taught me that time is really effing hard to do perfectly, it is full of countless non-obvious corner cases. Some of which will only bite you two years into deployment.