Re: Prevent running in Rosetta
Re: Prevent running in Rosetta
- Subject: Re: Prevent running in Rosetta
- From: j o a r <email@hidden>
- Date: Tue, 27 Dec 2005 22:45:11 +0100
On 27 dec 2005, at 18.21, Rosyna wrote:
Aren't these both problems on your end? If they don't work in
Rosetta because an API changed, then file a bug on Rosetta. If they
don't work because of a bug in your code, fix the bug. Don't just
go an disable your app based on the return value of kern_sysctl's
KERN_CLASSIC (44) or sysctlbynames's return of "hw.optional.mmx" as
that's just placing the blame somewhere else and doesn't do
anything to help the other developers with this problem (APIs not
working in Rosetta).
The end users would not be happy if many apps do this (say, to
force an upgrade charge) and apple would not be happy if you
needlessly blame them for bugs in your code.
You talk a lot about blame, while I couldn't care less. I just want
to provide our users with the best experience, while at the same time
allowing us to spend our resources where they make sense.
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'm just looking for a transition fix, and an Info.plist key to
control this behaviour would in my opinion be perfect. A small
runtime check would be unfortunate, but acceptable.
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... ;-)
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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