Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!overload!dillon From: dillon@overload.Berkeley.CA.US (Matthew Dillon) Newsgroups: comp.sys.amiga.programmer Subject: Re: Lemmings - a tutorial Part IV Message-ID: Date: 4 Apr 91 21:26:36 GMT References: <23787@well.sf.ca.us> <1991Mar31.195148.6667@starnet.uucp> <24001@well.sf.ca.us> Organization: Not an Organization Lines: 56 Mr Farren, you could not have put this argument in better perspective, I agree with you 100%! -Matt In article <24001@well.sf.ca.us> farren@well.sf.ca.us (Mike Farren) writes: > >So don't use the Intuition environment. I don't - except for the initial >.. >The OS also does not prevent you from doing those things. >... >So if you don't want to share, just let the OS know. It'll cooperate >with you. >... >Only in the high-speed arcade game field. None other. >... >My only point! Damn it, I didn't say that taking over the machine was >never to be done, I said that you shouldn't do it unless you need to, and >you should clean up after yourself when you do. >... >Bull. If piracy is such a problem, why is it that nearly all the games >for the IBM PC (which has a MUCH higher piracy rate than the Amiga) can >be installed on HD's? Why haven't all the IBM PC software companies gone >broke by now? >.. >Yep. 80K, measured after startup-sequence, including mounted drives, not >including Workbench screen memory (which returns to the system after you >CloseWB(), as long as nothing else is running - the situation in an autoboot >512K A500 game). Not to mention the fact that if a game is THAT close to going over the 512K edge it might be a good idea to write it for a 1M machine anyway. As has been mentioned, $80 will bring you up to 1M. >Only if you have it. If you don't HAVE 1M, go ahead, take over, nobody's >going to care. >.. >Not really. There are much more sophisticated graphics tools out there. >.. >Algorithm A: 8 hours implementation time, including debugging, in C - >32 hours, including implementation time, in asm. How many times will >you have to run it to recoup that 24 hours? Assembly where you need it, >C where you don't. You don't ALWAYS use C (at least, I don't), but you >don't always use assembler, either. > >-- >Mike Farren farren@well.sf.ca.us -- Matthew Dillon dillon@Overload.Berkeley.CA.US 891 Regal Rd. uunet.uu.net!overload!dillon Berkeley, Ca. 94708 USA