• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Apple's Tools Strategy
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Apple's Tools Strategy


  • Subject: Re: Apple's Tools Strategy
  • From: "Andy O'Meara" <email@hidden>
  • Date: Sun, 29 Oct 2006 09:45:01 -0400
  • Thread-topic: Apple's Tools Strategy

I don't think this thread is getting anyone anywhere--it should probably
stop.

Xcode 3 is right around the corner, so there's new features not too far
away...  As a recovering CodeWarrior fanboy, even I have to admit that by
Xcode 3, there'll very very few categories remaining that Codewarrior
remains superior.  Let's just hope the major version change is justified.

Or, as Chris mentioned, if Xcode is that critical to your way of life, get a
Select ADC membership and you can get involved.


Andy





On 10/29/06 7:05 AM, "Turtle Creek Software" <email@hidden>
wrote:

>> Call me unrealistic or even a snob, but the nature of the work we do
>> is such that anyone doing it should have above average analytical
>> skills and be able to express his thoughts. Anyone using Xcode should
>> be able to offer more than "It needs to be better," especially if
>> he's used something he thinks *is* better, as you apparently have.
>
> I think the radar system works extremely well, the times I have used
> it.  However, in this case, I haven't spent enough time with XCode to
> be able to describe the problems well enough for the radar system.
> Hence the vague complaints.
>
> But maybe it's time to reframe the issue.  I think the larger problem
> is that the Apple tool situation changed dramatically last year, and
> that may require a matching change in Apple's role.
>
> For a while, Think Pascal/C was the development platform of choice for
> many developers, then CodeWarrior took over.
>
> However, now there is no alternative development platform created by
> some company that HAS to make the product user-friendly, or lose money.
>  And I guess you're right, with a free competitor, there is little
> chance a competing/better product will ever appear again.
>
> Does Apple really WANT to be the monopoly provider?  If so, then I
> think it had better find a way to make XCode more 'elegant', or risk
> losing the most creative new developers (and some old ones).  That
> probably means listening more to vague complaints, and addng some of
> the GUI design elegance that appears in other Apple products.  Or get
> that elegance from a retired product GUI that already had it.
>
> If not, then it's time to do something to foster competition, and
> quickly.
>
> Dennis Kolva
> Turtle Creek Software
>  _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
>


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: Apple's Tools Strategy (From: Turtle Creek Software <email@hidden>)

  • Prev by Date: Re: Apple's Tools Strategy [was: Accessing function definitions Radar]
  • Next by Date: Re: What is the meaning of "missing indirect symbols for section (__TEXT, __symbol_stub)"?
  • Previous by thread: Re: Apple's Tools Strategy
  • Next by thread: Re: Apple's Tools Strategy
  • Index(es):
    • Date
    • Thread