From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_05E4_01C75B81.74F4AF50
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   And for the programs you write, go ahead and do what you think is =
best.  Other strategies have been more successful.

Rich

  "Don Hills"  wrote in message =
news:Nbm5FtgaXmEV092yn{at}attglobal.net...
  In article , "Rich"  wrote:
  >
  >   I disagree.  It all depends on your strategy for portability.

  Well, you would disagree, wouldn't you? I have a different viewpoint: =
if I
  were writing an application with a brief to run it on as many =
platforms as
  possible, I'd write it to the *ix architecture to minimise my work and
  support load. Once you consider Windows as just one of the many OSes =
to be
  supported, it's the logical way to go.

  --=20
  Don Hills
------=_NextPart_000_05E4_01C75B81.74F4AF50
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   And for
the programs you =
write, go=20
ahead and do what you think is best.  Other strategies have been = more=20
successful.
 
Rich
 

  "Don Hills" <black.hole.4.spam{at}gmail.commailto:black.hole.4.spam{at}gmail.com">black.hole.4.spam{at}gmail.com
A>>=20
  wrote in message news:Nbm5FtgaXmEV092yn{at}attg=
lobal.net...In=20
  article <45e59b7f$1{at}w3.nls.net>,">mailto:45e59b7f$1{at}w3.nls.net">45e59b7f$1{at}w3.nls.net>,
=
"Rich"=20
  <{at}>
wrote:>>   I
disagree.  It all =
depends=20
  on your strategy for portability.Well, you would disagree, =
wouldn't=20
  you? I have a different viewpoint: if Iwere writing an application =
with a=20
  brief to run it on as many platforms aspossible, I'd write it to =
the *ix=20
  architecture to minimise my work andsupport load. Once you =
consider=20
  Windows as just one of the many OSes to besupported, it's the =
logical way=20
  to go.-- Don =
Hills   

------=_NextPart_000_05E4_01C75B81.74F4AF50--

--- BBBS/NT v4.01 Flag-5