Deutsch   English   Français   Italiano  
<v7s2gd$jch$1@panix2.panix.com>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!weretis.net!feeder9.news.weretis.net!panix!.POSTED.panix2.panix.com!panix2.panix.com!not-for-mail
From: kludge@panix.com (Scott Dorsey)
Newsgroups: rec.arts.sf.written,rec.arts.comics.strips
Subject: Re: xkcd: CrowdStrike
Date: 24 Jul 2024 23:25:01 -0000
Organization: Former users of Netcom shell (1989-2000)
Lines: 20
Message-ID: <v7s2gd$jch$1@panix2.panix.com>
References: <v7mhb5$qi0k$2@dont-email.me> <v7o7b5$fer$1@panix2.panix.com> <95mv9jpkr8usskbq56cgfu20mn65b3n8v6@4ax.com> <lgackjFnp00U1@mid.individual.net>
Injection-Info: reader1.panix.com; posting-host="panix2.panix.com:166.84.1.2";
	logging-data="4796"; mail-complaints-to="abuse@panix.com"
Bytes: 1725

Mark Jackson  <mjackson@alumni.caltech.edu> wrote:
>
>Well, absent a countervailing force the capitalist imperative 
>discourages carrying the cost of robustness, and eventually eliminates 
>it entirely.  Do you have a suggestion other than regulation?

The government could regulate.  But on the other hand, the government
also could put money into development of reliable computing systems
and code verification techniques.  But more importantly, into transferring
that information into the hands of people willing to make actual products.

We've had actual verified kernels since the seventies, although for
very limited applications (and having to use interrupts makes everything
much much harder... Honeywell avoided a lot by avoiding interrupt-driven
I/O at the expense of performance).  Don't even get me started about the
iAPX 432 which was a bad system with some great ideas that were never
carried forward.
--scott
-- 
"C'est un Nagra. C'est suisse, et tres, tres precis."