Path: utzoo!attcan!uunet!cs.utexas.edu!usc!apple!mips!pacbell.com!pacbell!rtech!beaver!sbrooks From: sbrooks@beaver..UUCP (Steve Brooks) Newsgroups: comp.arch Subject: Re: Macintosh OS Keywords: Macintosh, OS Message-ID: <5450@rtech.Ingres.COM> Date: 13 Jun 90 16:52:54 GMT References: <1943@key.COM> <1990Jun7.212351.20426@calgary.uucp> <6570@scolex.sco.COM> <8767@odin.corp.sgi.com> <26765.26701754@vaxb.acs.unt.edu> <4242@darkstar.ucsc.edu> <2922@demo.COM> <1990Jun12.163321.676@agate. Sender: news@rtech.Ingres.COM Reply-To: sbrooks@ingres.com (Steve Brooks) Organization: Ingres Corporation. Lines: 50 In article <1990Jun12.163321.676@agate.berkeley.edu> dankg@volcano.Berkeley.EDU (Dan KoGai) writes: >In article <2922@demo.COM> jgk@osc.COM (Joe Keane) writes: > > >>Certainly the Macintosh's user interface is a step forward (never mind Apple >>took it from Xerox). But the OS is a giant leap into the 50s. Everything we >>know about interrupts and scheduling is thrown out the window. Remember what Well Put. > >computer is an expensive gadget and must be shared. Macintosh, on the other >hand is a child of personal computer: 100% CPU time is yours (or your >sessions, to be more exact). You are comparing Apple to Orange. That's perfectly fine if you are 100% of the users. This whole discussion started because of the limited ability of the Macintosh to multitask. You can't give 100% CPU time to all "sessions". > >>You know, it's too bad you can't hit control-T to see what your Macintosh is >>trying to do; of course one reason is that the stupid thing doesn't have a >>control key. Now that's something that makes the user feel in control, even >>if it doesn't actually do anything. > > While you understand computer, you don't understand Macintosh. Is this discussion now going to change from "MacOS is not an OS" to "Macintosh is not a computer" ?? >Control Key is a no-no concept for Macintosh: That makes programmer's works >hard because you have to program a bullet-proof software. But it obviously So Macintosh programmer's don't have to write bullet-proof software ?? No wonder the Mac is having trouble gaining acceptance. >benefitted users. The best thing Macintosh did was telling us computers are >for users, not for programmer who program for programmer's sake. > And if you have Programmer's key INIT, you can easily interrupt with >ADB keyboard. And if you have TMON, you can use degubber with window. Now Yeah, right. The Mac is "for users", but to really accomplish anything you need TMON. Let's get back to comp.arch ===== SjB. My Opinions.