🚀 go-pugleaf

In article <725@unccvax.UUCP> cbenda@unccvax.UUCP (carl m benda) writes:
>In article <869@apple.UUCP>, tecot@apple.UUCP (Ed Tecot) writes:
>> I posted this to INFO-MAC a while ago, but I was informed that some
>> people might not read comp.sys.mac.digest, so I'm posting again here:
>> 
>> What makes programming for the Macintosh difficult?  What would you like
>
>speed... look at c development on an unloaded vax 780 running BSD 4.3...
>What I think most programmers would like to see is c development tools 
>and environment such as exists in a Unix programming environment.
>
>I personally would like to see the ability to create c code using the text
>editor of my choice and then leave the editor (using switcher), going to 
>the finder and typing cc filename and with in 30 seconnds I would like to
>be able to double click the a.out icon.

How often do you get to use an unloaded vax 780?  And who is this wonderful
company that gives every programmer their own 780?

I use LightspeedC on a Mac with a DataFrame 40XP and this system will meet or
beat your 30 second limit for most single file recompiles.  It is mostly CPU
bound, so with a '20 add-on, it should beat an unloaded 780!  Oh, and I don't
have to type cc filename (trying to get the filename right) or make or anything,
I just hit cmd-R, with 15 seconds and I'm in my application.

The real problem with programming the mac is the learning curve.  There are
five volumes totaling well over 1000 pages of documentation for the OS, not
even including tech notes.  Once you figure out how to do something, it's
a lot faster to use the toolbox then to write it yourself, but learning the
toolbox is the major problem.  

>
>/Carl
>...decvax!mcnc!unccvax!cbenda

Jerry Whitnell
Communications Solutions, Inc.