🚀 go-pugleaf

In article <C0r8Ew.Cyx@gpu.utcs.utoronto.ca> gbcusg@gpu.utcs.utoronto.ca (I. Barnett) writes:
>Game writers have no choice but to search through the OS for tricks to
>use.

They don't *have* to be so lazy.  The information is out there; you
just have to look a bit.  I'm not saying game programmers suck, or STOS
sucks either.  I'm just saying that all the things that don't work on
STe's, TT's, Falcon's, etc., COULD have been written to work fine ahead
of time without impacting the speed.  I know because I've been part of
a project that's very much along those lines.  And yes, it was more work,
but it was time well-spent, IMHO.

>Developers are the most important resource a hardware vendor has and
>Atari has shown their developers absoultely no respect.  No wonder
>Atari's programming 'rules' are being broken by programmer.

I'm not going to disagree with that at all.  Atari made mistakes
regarding their dissemination of information to developers.  But
the situation is not so bad that you're forced to break the rules.

Dave Baggett
--
dmb@ai.mit.edu           MIT Artificial Intelligence Laboratory                  
ADVENTIONS: interactive fiction (text adventures) for the 90's!
dmb@ai.mit.edu *** Compu$erve: 76440,2671 *** GEnie: ADVENTIONS