🚀 go-pugleaf

In article <3637@brunix.UUCP> omh@zaphod.UUCP (Owen M. Hartnett) writes:
>
>Why does there have to be a reason?  Why not just put up a flag in Sysenvirons?
>Apple DTS always seems to have the attitude that it knows best what 
>developers should know about (or rather, not know about).  There may be
>developers out there with legitimate need to know - to fix bugs, to implement
>a novel feature, or for reasons yet unknown.
>
>If the information is available, and properly documented that there
>should be no reasons for using it (that we are currently aware of), then
>the programmer will know he has to take the responsibility for using it.
>
>True, some developers will misuse it, but then it's their problem.

  It's not true that it's merely "their problem" is some (commercial)
developers write bad software.  For any machine, it success or failure
is, to a large extent, determined by the commercial software that exists 
for it.  This is particularly true for the Mac.  As we all know,
the consistency of the 3rd party software has being a major factor in its
success.

  If apple expects to make all or many of MF's features standard aspects
of the OS itself, it would be just asking for trouble by encouraging
people to build MF-dependent applications.  If you are simply asking for
short-term solutions that will cease to work very soon, then just test for
the temporary memory allocation calls or something like that.

  Gregory Dudek

-- 
Dept. of Computer Science (vision group)    University of Toronto
Nice mailers:  dudek@ai.utoronto.ca
UUCP: {uunet,decvax,linus,pyramid,
		dalcs,watmath,garfield,ubc-vision,calgary}!utai!dudek
ARPA: user%ai.toronto.edu@relay.cs.net