home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pmafire!news.dell.com!natinst.com!cs.utexas.edu!sun-barr!news2me.EBay.Sun.COM!seven-up.East.Sun.COM!sungy!news.Sweden.Sun.COM!swippy!seunet!pop!bjst
- From: bjst@sth.frontec.se (Bjorn Stenberg)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: New hardware reference guide?
- Message-ID: <1992Nov11.124537.21704@sth.frontec.se>
- Date: 11 Nov 92 12:45:37 GMT
- References: <1992Nov4.134857.24783@sth.frontec.se> <BxGvwE.4op@visix.com>
- Organization: IDK/Frontec - System Design Group
- Lines: 25
- Nntp-Posting-Host: pop.sth.frontec.se
-
- bjst@sth.frontec.se (Bjorn Stenberg) writes:
- > > By not releasing hard core hw specs CBM can limit the amount of poorly
- > > written software produced.
-
- brett@visix.com writes:
- > Please! Hitting the hardware != POORLY Written Software
-
- Sure, there's lots of shit banging the hardware and works. Unfortunately,
- there's even more shit banging the hardware which does *NOT* work.
-
- I think saying that 'the less people are hitting hardware the more programs
- are likely to work well' is a pretty fair statement.
-
- Problems arise because when our friend the hacker gets 250+ registers to
- schmack and hit anyway he likes, he's likely to do something wrong.
- If he instead gets a few simple, properly written routines to do it, he'll
- have a greater chance of getting away with what he wants to accomplish.
-
- I never said -all- hardware hitting software was bad software.
-
- -- Bjorn
-
- /// Bjorn Stenberg, Stockholm, Sweden bjst@sth.frontec.se
- /// main() { printf(&unix["\021%six\012\0"],(unix)["have"]+"fun"-0x60);}
- \\\ /// "- Your documentation no longer confuses me, old version!"
-