Path: utzoo!attcan!uunet!hodge!pnet06!bruceh From: bruceh@pnet06.cts.com (Bruce Henderson) Newsgroups: comp.sys.mac.programmer Subject: A/UX polishing a @#$* Message-ID: <266@hodge.UUCP> Date: 6 Jul 88 00:02:10 GMT Sender: rusty@hodge.UUCP Organization: People-Net [pnet06], Orange, CA Lines: 41 It's been 5 or 6 months since Apple introduced A/UX. And so far the reaction to it has been pretty dead from their tried and true... the independent 3rd party developer. As a matter of fact, even their "Blue Chip" vendors are not porting over. As an A/UX user and a Mac developer of a few years, I can understand why. So far Apple has yet to unleash the power of the Mac II's ROMs. Sure, a bunch of stuff is implemented, and the rest is due "real soon now", but still, I think A/UX has a long way to go before it has people loosing their lunches in excitement over this thing. But let's look in the crystal ball for a moment. The day will come when Aplle will have Xwindows or NEWS or both up on A/UX. The real leverage of this system is that it may one day allow some of the better software packages in the industry to migrate to the workstation evironment. How? well on that magic day when all of the Mac II's ROMs are availabe to an A/UX compiler [either apple's c that is supplied with A/UX or a 3rd party Pascal] and Developers are able to compile original source code with little or no modification, then watch out! From that point calls to the diffrent "look and feel" routines can be swapped out to UNIX portable calls and a portable product can be created. I know that is sounds kind of far fetched, but it is what we intend to do with our next product for the Mac II, the development of which Kicks off next week. So, yes A/UX needs a lot of polish, and a lot more in the function department. But HEY! it has the best UNIX manuals of any I've ever seen! Bruce Henderson asm... [for you non MPW types, thats assembly commando] [pnet06] UUCP: hodge.cts.com!pnet06!bruceh ARPA: hodge!pnet06!bruceh@crash nosc.mil INET: bruceh@pnet06.cts.com