Xref: utzoo comp.sys.ibm.pc:40677 comp.sys.mac:45040
Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!usc!ucsd!helios.ee.lbl.gov!nosc!crash!pnet01!jca
From: jca@pnet01.cts.com (John C. Archambeau)
Newsgroups: comp.sys.ibm.pc,comp.sys.mac
Subject: Re: IBM vs. Mac - Long (was Re: Xerox sues Apple!!!)
Message-ID: <970@crash.cts.com>
Date: 24 Dec 89 01:56:02 GMT
Sender: root@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 44

kk@mcnc.org (Krzysztof Kozminski) writes:
>In article <5842@eos.UUCP> woody@eos.UUCP (Wayne Wood) writes:
>>That GUI you're so damned proud of is a nuisance.  When i want to grab a
>>port, or read a file (...) i don't want the machine to tell me i can't
>>access a file because it wasn't created by the application... i want the
>>goddamn file!
>
>Obviously, you're confused ... just goes to show your ignorance in the
>subject.  If you knew what you were talking about, you'd know that it is no
>big deal to write a program that will open and read any file ...
>
>>it took me three months to create an application on a MACII that only took
>>me two weeks to create on a *NIX machine.  Productivity?  BULLSHIT!
>
>Meadow muffins.  Any time I have to write a standalone application that does
>not require UNIX-specific system calls and lex/yacc, I'd do it on a Macintosh
>precisely for the reasons of productivity.  Think C compiles on a Mac II in
>half the time of a VAX 8650 - I am talking CPU time here - the real time can
>be 1/10 of a moderately loaded 8650 ...
>
>Where I used to work, the command-line based applications for IBM would
>be written on a Mac Plus, then transferred and compiled on an IBM AT
>(it was a couple of years ago).  I remember it used to take 20 minutes on
>an AT with a hard disk to compile a program that took 2 minutes on a
>Plus with floppies.

One thing that's a bloody nuisance in developing PORTABLE applications, and I
emphasize PORTABLE is the damn graphics interface.  Quite a few of the C
compilers out there do NOT support environment variables (i.e. getenv, putenv)
unless they 'fake' a command interpreter that supports environment variables. 
Then you have the annoyance of creating the menus that have no use in the Unix
environment (unless there's a graphics interface such as X-Windows or
SunView).
 
     // JCA

 /*
 **--------------------------------------------------------------------------*
 ** Flames  : /dev/null                     | My opinions are exactly that,
 ** ARPANET : crash!pnet01!jca@nosc.mil     | mine.  Bill Gates couldn't buy
 ** INTERNET: jca@pnet01.cts.com            | it, but he could rent it.  :)
 ** UUCP    : {nosc ucsd hplabs!hd-sdd}!crash!pnet01!jca
 **--------------------------------------------------------------------------*
 */