Path: utzoo!utgpu!attcan!uunet!husc6!cmcl2!nrl-cmf!ames!ncar!oddjob!gargoyle!att!occrsh!uokmax!rob From: rob@uokmax.UUCP (Robert K Shull) Newsgroups: comp.sys.mac Subject: Re: 6.0 What works - what doesn't? Message-ID: <1680@uokmax.UUCP> Date: 10 Aug 88 18:06:23 GMT References: <7988@cup.portal.com> <5832@batcomputer.tn.cornell.edu> <9713@dartvax.Dartmouth.EDU> Reply-To: rob@uokmax.UUCP (Robert K Shull) Organization: University of Oklahoma, Norman, OK Lines: 24 In article <9713@dartvax.Dartmouth.EDU> earleh@eleazar.dartmouth.edu (Earle R. Horton) writes: >MicroSoft delibrately takes shortcuts which they know will compromise >the future integrity of their software, or that Apple Computer Company >does not fully document their operating system, perhaps even >internally. I know what I believe. This kind of thing becomes a I've used Microsoft products since the early Apple ][ days, and I know what I believe. It doesn't surprise me at all that they (and a great number of other companies) ignore the published info in favor of speed, compactness, or maybe just laziness. It's kind of interesting to haul out old software when a new system release comes out, and see what still works. I've noticed something: a great deal of software doesn't work on a Mac II, doesn't work under Multifinder, doesn't work under System 6.0, etc, individually or together. The software that DOES work on one of these usually works on them all. I've seen a LOT of obvious mistakes (things that break on a Mac II that were "bad practice" in IM vol. 1) I don't mean that Apple never changes things, but I think a lot more of the problems are caused by "cheating" than by changes from Apple. Robert -- Robert K. Shull University of Oklahoma, Engineering Computer Network att!occrsh!uokmax!rob CIS 73765,1254 Delphi RKSHULL sun!texsun!uokmax!rob