Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!rpi!uupsi!grebyn!ckp From: ckp@grebyn.com (Checkpoint Technologies) Newsgroups: comp.sys.amiga Subject: Re: Difficulty in programming Message-ID: <20108@grebyn.com> Date: 5 Jun 90 19:51:33 GMT References: <2487@zipeecs.umich.edu> <1990Jun2.063414.10292@agate.berkeley.edu> <20990@estelle.udel.EDU> <1990Jun4.191035.12599@watdragon.waterloo.edu> <1990Jun5.084107.162@agate.berkeley.edu> Reply-To: ckp@grebyn.UUCP (Checkpoint Technologies) Organization: Grebyn Timesharing, Vienna, VA, USA Lines: 27 In article <1990Jun5.084107.162@agate.berkeley.edu> laba-1ei@e260-3c (Joseph Chung) writes: > >Since I posted the original REPLY that generated so much flames, I feel that >I must clarify my position. I in no way endorsed the IBM PC when I said it >was easier to program. I own an Amiga and I like it very much, (yea even >programming it!) > >Now, maybe all your emminences out there can help a little guy out. I've >toyed with the Pets, 64's, AppleII's, IBM's, and Amigas, and in all cases I >found it easier to get things done on everything else but the Amiga. If you're really interested in a simple Amiga programming environment, then you should read the Bantam AmigaDOS manual and nothing else. Then you can use Read() and Write() with CON: for input and output, and it's about as simple as you want it to be. You can even get mouse click messages, raw keycodes, and window configuration information. But if you think that doing windows, menus, gadgets, requesters, screens, views and viewports, bobs, sprites, and such sophisticated Amiga things, when acting as a task in a multi-tasking system, should be as simple as doing single-tasking text applications on the IBM, then you are just going to be dissapointed. Get used to it. -- First comes the logo: C H E C K P O I N T T E C H N O L O G I E S / / \\ / / Then, the disclaimer: All expressed opinions are, indeed, opinions. \ / o Now for the witty part: I'm pink, therefore, I'm spam! \/