home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!lysator.liu.se!marvil
- From: marvil@lysator.liu.se (Martin Vilcans)
- Subject: Re: New hardware reference guide?
- Message-ID: <1950@lysator.liu.se>
- Sender: news@lysator.liu.se
- Nntp-Posting-Host: robin.lysator.liu.se
- Organization: Lysator Academic Computer Society, Linkoping University, Sweden
- References: <Bx7782.CKD@kingston.ac.uk> <1992Nov5.184916.17436@sth.frontec.se> <1927@lysator.liu.se> <BxAMtH.Aos@cck.coventry.ac.uk>
- Date: Wed, 11 Nov 1992 20:33:05 GMT
- Lines: 26
-
- csg019@cch.coventry.ac.uk (-~=Zaphod=~-) writes:
-
- >>No, most demo programmers can't do OS programming very well, and are
- >>probably too lazy to learn about it. And, as demo coders are speed freaks,
- >>they won't like using someone else's code, as they can't trust it's as fast
- >>as they could have made it (and it isn't probably, as OS code should be very
- >>flexible).
-
- >Whoa! Thats crap. Demo programmers use the hardware for speed only, it has
- >nothing to do with lazyness. Its true, we don't like using other peoples code,
- >because we would not be able to accomplish what we set out to do.
-
- Coding the hardware is, if not easier to do, easier to learn. And you don't
- need lots of expensive books for it either. And it is actually harder to
- follow the rules of OS programming than the rules of hardware programming,
- so OS-coded demos will _not_ work better than hardware coded ones. Most
- demo coders are not the persons to follow rules.
- (And I am a demo coder as well, and have played around a bit with the OS
- and Intuition, so I know what I'm talking about.)
-
- >The fact is, what ever you can do in the OS in 4 frames using the OS, a good
- >demo programmer would probably do in 100 raster lines, and make it work on
- >any machine.
-
- Yes, that's right.
-
-