<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 3/12/19 3:39 PM, William Herrin
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAP-guGV2btSnBaWG+M8YzoduV7XwZ1_AD4x8VH3cwXZP7W++hw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
On Tue, Mar 12, 2019 at 2:50 PM <<a
href="mailto:valdis.kletnieks@vt.edu" moz-do-not-send="true">valdis.kletnieks@vt.edu</a>>
wrote:<br>
> On Tue, 12 Mar 2019 13:45:23 -0700, William Herrin said:<br>
> > In many cases, only the foreground app has a clear
understanding of the<br>
> > state of the screen. Not the OS and definitely not the
hardware platform.<br>
> > I'd be super pissed if I died in Overwatch because the
BIOS tried to take<br>
> > over the screen to display an amber alert.<br>
><br>
> Would you be super pissed if you died for real because
Overwatch suppressed a<br>
> tornado or other severe weather alert relevant to your
location? Serious<br>
> question here.
<div><br>
</div>
<div>I'd prefer if my computer's BIOS didn't talk to the network
at all, that being far more likely to open a path for malware
than to save me from a tornado. Some things just have "bad
idea" written all over them. Serious answer.</div>
<div><br>
</div>
</div>
</blockquote>
<p>What's with perpetuating the thought that it needs to be in the
bios? It's just a normal app on a normal computer like Biff.</p>
<p>Mike<br>
</p>
</body>
</html>