Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!apple!dlyons
From: dlyons@Apple.COM (David A. Lyons)
Newsgroups: comp.sys.apple2
Subject: Re: DTS
Message-ID: <52446@apple.Apple.COM>
Date: 4 May 91 05:24:05 GMT
References: <9JXc23w164w@xcluud.sccsi.com>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 65

In article <9JXc23w164w@xcluud.sccsi.com> gtolar@xcluud.sccsi.com (Glynne Tolar) writes:
>[...] 
>I talked to Andrew at CV Technoligies eariler today.  He explained to me in 
>what I caused to be a lengthy conversation that he was a developer that 
>paied the $600 a year (yes, I know it is now $300 and I did correct him) and 
>he said "And you know what I get for the $600?  A bunch of Mac crap."  Now 
>no flame here Matt but what is the deal?

That picture of the Apple Partners program is incomplete.  For $300 you get
a monthly mailing, including Apple II Technical Notes every other month (for
$600 you get Macintosh Technical Notes in the other other months).  You get
significant discounts on a limited (not tiny) amount of equipment per year.
You get official access to Developer Technical Support.


>My personal observation...That is Apple's idea of Apple II developer 
>support.  Send Mac developement materals, develope on the Mac (for II 
>software, how strange).  Explains the 2 Macs in Andy's cube.

If you want to see things that way, I can't convince you not to.  Here's
how I see it:

(1) Sounds like CV Technologies paid their $600 and is receiving information
on both the Macintosh and Apple II lines.  And they're probably getting LOTS
of Macintosh stuff--not surprising considering the impending release of
System 7.0, etc.

(2) Developing Apple II software on a Macintosh is not at all strange.  It's
not the solution for everybody.  For me and my coworkers it's the obvious
choice because of the following things I can do on a Mac running MPW that
I can't do on a GS, at least not with today's hardware and software:

   (a) Use a 20-inch screen with many windows open.

   (b) Use the Projector project-management system to make sure only one
       person is using a given source file at one time, and to provide
       access to the "history" of our source code ("Not all changes are
       improvements").

   (c) Rebuild large software modules quickly.

   (d) Keep the GS systems free to test out the latest-and-greatest version
       every time I make some changes.

I use an 8 Meg Macintosh IIci at work.  So what?


>[...] if Apple II software engineers are just trainees for future jobs in Mac 
>developement.

Not me.

>[...] Problem is, should be settle for just 
>the bones Apple throws our way or is their going to be any meet anytime.

(Loaded question?  Nah....)  My opinion:  You should continually be as
productive as possible with whatever is available, paying little attention
to gloom-and-doom rumors *or* "System 12.0 / ROM 42" rumors.
-- 
David A. Lyons, Apple Computer, Inc.      |   DAL Systems
Apple II System Software Engineer         |   P.O. Box 875
America Online: Dave Lyons                |   Cupertino, CA 95015-0875
GEnie:DAVE.LYONS  CompuServe:72177,3233 Internet:dlyons@apple.com

My opinions are my own, not Apple's.