Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!olivea!apple!well!farren
From: farren@well.sf.ca.us (Mike Farren)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: How do we change the scheduler? (Was Re: Multitasking at home...)
Message-ID: <22780@well.sf.ca.us>
Date: 21 Jan 91 14:47:10 GMT
References: <42609@ut-emx.uucp> <1991Jan18.050529.13101@zorch.SF-Bay.ORG> <42731@ut-emx.uucp> <1991Jan19.035418.15192@zorch.SF-Bay.ORG> <42792@ut-emx.uucp>
Lines: 28

awessels@ccwf.cc.utexas.edu (Allen Wessels) writes:
>As I understand them, desk accessaries reside primarily on disk with a pointer
>to the code on disk.    The desk accessory is invoked via a menu.

You do not understand them.  Desk accessories become part of the system
file, unless you are running a utility like "Suitcase".  They absolutely
take up RAM.

>With 16 Mhz 286s with 256 color VGA and Windows machines running around $1500,
>some of those advantages are starting to blur.

Nope.  They're getting clearer, as you find that you STILL can't get the
capability of a $500 Amiga 500 on anything short of a $1500 '386 machine,
and you can't get some of them even then.

>Porting is just a matter of what your development enviroment supports.

Get a life.  You don't understand porting at ALL.  A common library of
calls does NOTHING for you if you don't have the OS underneath those
calls.  How, for example, would you propose to simulate CreateProc() on
a Mac?  Or, for that matter, GetResource() on an Amiga?  You can't.

Sure, you can move BASIC programs back and forth, mostly.  But BASIC
is very far from being generally useful, and NEVER the language of
choice for professional work.

-- 
Mike Farren 				     farren@well.sf.ca.us