Path: utzoo!attcan!uunet!crdgw1!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!iuvax!att!oucsace!bchurch From: bchurch@oucsace.cs.OHIOU.EDU (Bob Church) Newsgroups: comp.sys.apple2 Subject: Re: MacMusings Message-ID: <2259@oucsace.cs.OHIOU.EDU> Date: 25 Oct 90 19:44:20 GMT References: <139800043@uxa.cso.uiuc.edu> <90295.214849SAB121@psuvm.psu.edu> Organization: Ohio University CS Dept., Athens Lines: 12 In article jh4o+@andrew.cmu.edu (Jeffrey T. Hutzelman) writes: >I agree. Apple II code always has been tight and clean; there's no >other way to do it on a 6502. >Jeffrey Hutzelman This training could be extremely handy. Given a machine that has a huge amount of memory and registers it's easy to get sloppy. It would be interesting to see the results of two programers on such a machine, one who has learned on the overpowered ( I know, contradiction in terms :-) ) machine and one who has learned on the //, when it comes time to program for multitasking, thus giving you many small computers.