Re: Prevent running in Rosetta
Re: Prevent running in Rosetta
- Subject: Re: Prevent running in Rosetta
- From: Ricky Sharp <email@hidden>
- Date: Tue, 27 Dec 2005 17:38:56 -0600
On Dec 27, 2005, at 3:45 PM, j o a r wrote:
We will provide UB apps, but I fear that there will be a period in
time when we have ppc binaries in the wild together with i386
machines. Rosetta is a new platform, quite comparable to the other
OS / hardware platforms that we support. Each platform that we
claim to support needs to be tested. Testing requires resources. I
don't know about you, but we have limited resources, and think it
would be insane to spend them on supporting Rosetta when our goal
is to provide UB at day one. Even if Rosetta would provide flawless
emulation, it still wouldn't cut it for our application - as our
performance requirements are too high.
I will also be in a similar situation. My existing flagship app is
Carbon (PPC). The new Cocoa version will be a univ binary. However,
some of my users will probably just want to keep the original Carbon
version (the Cocoa one will be a paid upgrade). In that case, I have
one of two choices:
(a) Do nothing to the app and just document on my web site that
running the app via Rosetta may not work correctly. While this does
seem harsh towards users, these are users that did spend money on new
hardware, yet no money on updating their apps. You can't make money
from such customers :)
(b) Qualify the app to run via Rosetta.
As with you, (b) is not an option for me. And although a Info.plist
key would be cool, that would still require users of the older PPC
software to "update" to get the plist modification. Users could
still run the original unmodified PPC app on an Intel Mac. So, I
think option (a) would make the most sense.
I'm a very much for reporting problems via Radar - but just like
Apple employees on this list have no obligation to answer
questions, I have no obligation to file bug reports. I'm absolutely
certain that I could spend 100% of my time filing bug reports, and
following up on the feedback I get back from Apple - but I'm
equally sure that my employeer wouldn't like that. You need to find
the right balance between spending time on influencing Apple to fix
the problems that matters to you, while on the other hand still
spending some time doing your job. Rosetta is transition technology
that we won't use for our application, so I will not spend time
trying to make it better. At least not while I'm at the office -
I'm such a Mac fan-boy I might still do it in my free time... ;-)
I would file the enhancement anyhow. While it may be the case where
you may not end up taking advantage of such a solution, it may help
others.
___________________________________________________________
Ricky A. Sharp
mailto:email@hidden
Instant Interactive(tm)
http://www.instantinteractive.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden