Re: Re: Apple's Tools Strategy
Re: Re: Apple's Tools Strategy
- Subject: Re: Re: Apple's Tools Strategy
- From: "Mark Munz" <email@hidden>
- Date: Sat, 28 Oct 2006 09:51:07 -0700
On 10/28/06, Turtle Creek Software <email@hidden> wrote:
1. Apple wouldn't need to BUY the Codewarrior source, just
license its interface code.
This a very generic request. What you need to do is document what
specific pieces of Codewarrior's interface are missing.
With the Condensed-mode in Xcode 2.3, you are about 85-90% of the way
to the CW look and feel. The differences are changes in paradigm (such
as the use of targets and configurations) which just work different
(and better IMHO) that CW.
2. If the above can't happen, then just steal as much of the
CW interface as is possible, or license the "look and feel".
It would be fine to make improvements, just make sure they
are improvements that the users want!
Again, generic "look and feel" helps nobody. Be specific. You can't
expect them to read your mind and quite frankly, I don't want Xcode to
just be a clone of CW. I've moved past that phase.
3. I'd be happy to pay money for a better development system.
Free and mediocre is not a good deal when it reduces the
Once again, generic statement. "better development system". What do
you mean by "better"? I have no clue what that means to you. As for
"Free and mediocre", Xcode is far from that and it sounds like you
don't have access to Leopard Developer Preview.
6. Fortunately, small companies can be profitable in places where large
ones can't. So even though Apple can't turn a profit on the
next great IDE, I have faith that some smaller folks eventually will,
a la Metrowerks.
If they can -- great! But I personally think that Apple is doing a
pretty good job with Xcode. No, it's not perfect -- but each release
significantly improves my productivity.
it's time to give us better tools!
Ugh! We all want better tools. Even CW doesn't meet that definition,
else there wouldn't have been 10 versions of it.
7. I'd be curious what % of developers used/use PowerPlant? We would
sure appreciate having an improved version of that for OSX, so we can
concentrate on coding features within our product niche, rather than
basic system functions.
Yes, there is an improved version -- it's called Cocoa! It is an
extremely rich framework that allows you to focus on your features
within your niche.
8. And as an extension of the above, being able to reduce the effort to
develop cross-platform would also be great. We actually build Mac
9/Mac X/Win versions from the same code base now, using a modified
PowerPlant. But that puts the burden on us to rewrite it for each new
OS and processor, and it seems like that would be better handled by
someone larger. Remember Bedrock?
This is the case with every OS. Windows now has .Net, Apple has Cocoa.
My experience with cross platform is that it always suffers from Least
Common Denominator unless you put tremendous effort. A better solution
that I've seen is to isolate your interface from the engine and write
the interface native to the OS.
It would be nice if someone would create a Obj-C -> CLR compiler and
basically map all the core foundation & appkit classes to .Net
equivalents. It would also be nice if everyone just used Macs!
--
Mark Munz
unmarked software
http://www.unmarked.com/
_______________________________________________
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