From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200110031355.f93DtZp13705@borja.sarenet.es>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Borja Marcos <borjamar@sarenet.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] vfork and paging
References: <20011003094521.3E7BF19A3C@mail.cse.psu.edu>
In-Reply-To: <20011003094521.3E7BF19A3C@mail.cse.psu.edu>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Date: Wed,  3 Oct 2001 15:55:34 +0200
Topicbox-Message-UUID: fbe8fb84-eac9-11e9-9e20-41e7f4b1d025

On Wednesday 03 October 2001 11:49, you wrote:
> writing correct programs is hard, but the addition of concurrency
> need not make it harder, and indeed if the problem
> includes concurrency (as with networks, file servers and interaction),
> having concurrency in the system and language can make it
> much easier to get it right, with structurally simpler solutions,
> compared to (say) the event driven schemes.

=09Concurrency demands a strong design, but that can give you a much simp=
ler to=20
understand program, and much easier to maintain. However, you need to be=20
careful.

=09Curiously, very few people write concurrent programs. Multitasking ope=
rating=20
systems are used as multiprogramming systems to run more than one program=
,=20
but most of those programs are sequential.

=09Is it a lost art? ;-)


=09Borja.