Article View: comp.sys.mac.oop.macapp3
Article #274Re: Re2: more ETO griping...
From: DRAPER
Date: Mon, 11 Jan 1993 20:58
Date: Mon, 11 Jan 1993 20:58
53 lines
2826 bytes
2826 bytes
Peter,
>Actually, I am old enough to remember both Microsoft and Borland producing
>tools for Macintosh development.
I think it takes a great leap of the imagination to consider Microsoft's
entries as *development tools*. QuickBASIC != QuickC | C version 5.x.
Borland's implementation of TurboPascal was fairly popular among many of my
friends in its day. But, it was almost abandoned from the beginning by
Borland. Was it ever a *development tool*? Where is TurboC++? What about
it's class library? What about debuggers? Where are the real _TOOLS_.
>Just to really throw sand back at you, Symantec (actually, Think) is probably
>more commonly used than Apple's tools.
So?
>I am not sure where you are coming from with your "disagreements." And I don't
>see the anti-trust issues. I do see some foolishness, though.
The only thing I disagree with is this statement:
>I just wonder why Apple doesn't put EVERYTHING into a subscription service
>(e.g. a high-end Partner program) and COMMIT to making everything available
>there. I don't understand why Apple doesn't see this in their interest. To m
ake
>themselves dependent upon third parties for the development tools is rather
>foolish in my opinion. Why did they do MacApp to begin with?!
Why? I think it's time that Apple started backing off. I think its time to
let other developers besides Symantec into the fray. I don't think it's
foolish for Apple to allow others to become part of a "total solution" for
the developer. That so called "dependance" can also be called
"opportunity" for third parties. Third party success in a stagnant market
such as development tools is necessary for Apple to develop market share.
For the small amount they're giving up, they are creating valuable
opportunities for third parties.
>Finally, regarding your last comment - "People need to stop complaining about
>what Apple doesn't do, and simply do it themselves" - you CANNOT possibly mean
>that all of us need to go out and write our own quirky class libraries and
>development tools...?!
>
No I don't. I meant the developer community as a whole producing tools for
itself, rather than waiting for Apple to get around to it for them.
|E|J- ED DRAPER
rEpar|D|<- Radiologic/Pathologic Institute
The University of Texas M.D. Anderson Cancer Center
draper@odin.mda.uth.tmc.edu
Technical Details
Message-ID:
<9301112054.AA08772@odin.mda.uth.tmc.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!howland.reston.ans.net!spool.mu.edu!olivea!apple!applelink.apple.comShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!howland.reston.ans.net!spool.mu.edu!olivea!apple!applelink.apple.com From: DRAPER@ODIN.MDA.UTH.TMC.EDU Newsgroups: comp.sys.mac.oop.macapp3 Subject: Re: Re2: more ETO griping... Message-ID: <9301112054.AA08772@odin.mda.uth.tmc.edu> Date: 11 Jan 93 20:58:00 GMT Sender: daemon@Apple.COM Organization: AppleLink Gateway Lines: 53