Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!cs.umn.edu!kksys!edgar!saylor!macgate!Uucp
From: Jim.Spencer@p510.f22.n282.z1.fidonet.org (Jim Spencer)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: fonts in stacks (was: Re: Simulating arrays (Of tickboxes))
Message-ID: <674629203.1@macgate.fidonet>
Date: 18 May 91 02:29:08 GMT
Sender: Uucp@p0.f22.n282.z1.fidonet.org
Lines: 23


Michael Weiss writes in a message to All

MW> See, the only rule Apple obeys is this: All Apple rules apply 
MW> to everyone else BUT Apple. This HAS to be true. Why else is 
MW> it that whenever a new Mac comes out, a new version of System 
MW> software comes out, too? If they were following their own rules, 
MW> the System software, like everything else should be compatible 
MW> with all future versions. And what about the ROMs? In every 68030 
MW> machine, the ROMs were supposed to be 32-bit clean. But were 
MW> they? No. So now, the machines that Apple has touted as being 
MW> ablt to address memory as a 32-bit clean machine would won't. 
MW> (sounds a bit difficult, but you know what I mean). I would like 
MW> to see, once and for all, Apple obey the rules that THEY THEMSELVES 
MW> started. I don't mind additions (like pop-up menus, and the like), 
MW> because they are supersets to the original rules. I hate it when 
MW> they completely and unabashedly violate the rules TO THE LETTER 
MW> (do exactly what the rules say DON'T DO). 
MW> Sorry. Enough flaming of Apple. (turning off acetylene tank) 

As far as Apple following its own rules, the only thing Apple has to do is guarantee that if someone follows the rules, Apple won't gratuitously break their code, a promise that for the most part Apple has kept.  The System and ROM code implement the rules so they can't, in themselves, obey the rules.
 
 * Origin: White Mailer Test Point (1.0d6) (1:282/22.510)