![]() | This article is rated B-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||||||
|
Is Rosetta really an emulator, or just a compatibility layer? —Preceding unsigned comment added by 200.195.79.39 ( talk • contribs) 21:59, 7 June 2005
Is it a dynamic recompiler, or is not enough known yet for this to be answered? —Preceding unsigned comment added by 60.240.224.235 ( talk • contribs) 10:33, 8 June 2005
Alistair, to address the points you made in your discussion with Steven_Fisher, the fact that Rosetta doesn't directly emulate a PowerPC processor only means that it is not a low-level emulator. The fact that Apple and Transitive never call it an emulator is because in marketing terms, consumers read "emulator" to mean "s..l..o..w....." MFNickster
is this really a stub? I think the stub qualifier should be removed... there probably isn't much else to say about this topic, and its a decently long article. —Preceding unsigned comment added by 130.132.143.49 ( talk • contribs) 00:11, 14 July 2005
How does Rosetta compare with:
I've used both systems, and I was particularly impressed with FX32!. FX32! was rather slow the first few times you ran a particular app. But after that, the speed picked up dramatically. I gather that it profiled the emulated code as it ran, then during idle time it would optimize heavily used portions of code and store the result for use when running the application in the future. The system worked very well. We never had any problems running complex apps like Photoshop on our Alphas. Native Apps for the Alpha were pretty few and far between. It was never more than a niche player in the world of WinNT.
Apple's 68000 emulator was a very transparent experience, for the end user there was no sign that an application was not native PPC (even portions of the OS were run in emulation). However the emulator did not include an FPU, so some apps wouldn't work. You could get a shareware FPU emulator if you really needed one. Apple used FAT BINARIES to bundle 68k and PPC code together in one file. Since disc space was such an issue then, there were utilities that would strip out the unneeded portion of a binary file. It took a long time before everything one wanted to run was available in native PPC. It took Apple years to get all the 68K code out of the OS, as well. —Preceding unsigned comment added by 68.189.136.159 ( talk • contribs) 16:26, 14 July 2005
Is there a source for the statement that Rosetta won't handle Java applets in a web browser? That seems a fairly substantial shortcoming that I would expect to have been brought up more often, and this is the first place I've seen it stated. Tverbeek 12:53, 28 July 2005 (UTC)
Hello, I put in the addition about the applets running in web browsers. My source was from Apple developer guidelines on Rosetta at:
Universal Binary Programming Guidlines: What Can Be Translated?
As I understand it, Java applets should run without difficulty in x86-native browsers. However, they will not operate in a translated browser. So, for example, Internet Explorer, which I doubt will ever be recompiled by Microsoft as a Universal Binary, will run under Rosetta, but Java applets will not run inside said application. If I had to speculate as to a reason, perhaps it's not possible to translate both the browser itself and the PPC Java plugin, and it's not possible for the PPC-native browser to call the x86-native plugin.
(Oh, and if it's not appropriate to respond to talk page inquiries in the talk page itself, sorry. I'm new. Please correct me if I'm wrong.) —Preceding unsigned comment added by Crispy1083 ( talk • contribs) 04:55, 1 August 2005
That's exactly what you're supposed to do. Just remember to sign your comments, by putting ~~~~ at the end of them. Thanks. (And I wouldn't be so sure that IE won't be recompiled; MS may have stopped developing it, but they probably don't want their browser to be known as "the broken one".) Tverbeek 07:53, 1 August 2005 (UTC)
What's the performance hit from using Rosetta? —Preceding unsigned comment added by 209.240.239.139 ( talk • contribs) 15:11, 15 August 2005
An interesting point that I do not see covered would be "Where is Rosetta located in the system?" Is it embedded in the kernel? Or is it a file? Also, how does the process start? This information, of course, would only increase understanding of how OS X for Intel works.
Further to that, is such information deliberately concealed by Apple (probably for good reason)?
Should Rosetta 2 be incorporated into this article or have an article of its own? Herbfur ( talk) 20:13, 22 June 2020 (UTC)
With this in mind, it seems plausible to think Apple will retain support for Rosetta 2 within the macOS into at least 2023.
I've again removed mention of install-time translation per WP:V ("Any material that needs a source but does not have one may be removed"); "it was mentioned in the video at WWDC 2020" isn't sufficient. There's no mention of this feature at
https://developer.apple.com/documentation/apple_silicon/about_the_rosetta_translation_environment or the
https://developer.apple.com/videos/play/wwdc2020/10214 transcript, so someone would need to specify precisely which video. ...Found it in the keynote.
73.69.184.160 (
talk)
12:21, 21 August 2020 (UTC)
![]() | This article is rated B-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||||||
|
Is Rosetta really an emulator, or just a compatibility layer? —Preceding unsigned comment added by 200.195.79.39 ( talk • contribs) 21:59, 7 June 2005
Is it a dynamic recompiler, or is not enough known yet for this to be answered? —Preceding unsigned comment added by 60.240.224.235 ( talk • contribs) 10:33, 8 June 2005
Alistair, to address the points you made in your discussion with Steven_Fisher, the fact that Rosetta doesn't directly emulate a PowerPC processor only means that it is not a low-level emulator. The fact that Apple and Transitive never call it an emulator is because in marketing terms, consumers read "emulator" to mean "s..l..o..w....." MFNickster
is this really a stub? I think the stub qualifier should be removed... there probably isn't much else to say about this topic, and its a decently long article. —Preceding unsigned comment added by 130.132.143.49 ( talk • contribs) 00:11, 14 July 2005
How does Rosetta compare with:
I've used both systems, and I was particularly impressed with FX32!. FX32! was rather slow the first few times you ran a particular app. But after that, the speed picked up dramatically. I gather that it profiled the emulated code as it ran, then during idle time it would optimize heavily used portions of code and store the result for use when running the application in the future. The system worked very well. We never had any problems running complex apps like Photoshop on our Alphas. Native Apps for the Alpha were pretty few and far between. It was never more than a niche player in the world of WinNT.
Apple's 68000 emulator was a very transparent experience, for the end user there was no sign that an application was not native PPC (even portions of the OS were run in emulation). However the emulator did not include an FPU, so some apps wouldn't work. You could get a shareware FPU emulator if you really needed one. Apple used FAT BINARIES to bundle 68k and PPC code together in one file. Since disc space was such an issue then, there were utilities that would strip out the unneeded portion of a binary file. It took a long time before everything one wanted to run was available in native PPC. It took Apple years to get all the 68K code out of the OS, as well. —Preceding unsigned comment added by 68.189.136.159 ( talk • contribs) 16:26, 14 July 2005
Is there a source for the statement that Rosetta won't handle Java applets in a web browser? That seems a fairly substantial shortcoming that I would expect to have been brought up more often, and this is the first place I've seen it stated. Tverbeek 12:53, 28 July 2005 (UTC)
Hello, I put in the addition about the applets running in web browsers. My source was from Apple developer guidelines on Rosetta at:
Universal Binary Programming Guidlines: What Can Be Translated?
As I understand it, Java applets should run without difficulty in x86-native browsers. However, they will not operate in a translated browser. So, for example, Internet Explorer, which I doubt will ever be recompiled by Microsoft as a Universal Binary, will run under Rosetta, but Java applets will not run inside said application. If I had to speculate as to a reason, perhaps it's not possible to translate both the browser itself and the PPC Java plugin, and it's not possible for the PPC-native browser to call the x86-native plugin.
(Oh, and if it's not appropriate to respond to talk page inquiries in the talk page itself, sorry. I'm new. Please correct me if I'm wrong.) —Preceding unsigned comment added by Crispy1083 ( talk • contribs) 04:55, 1 August 2005
That's exactly what you're supposed to do. Just remember to sign your comments, by putting ~~~~ at the end of them. Thanks. (And I wouldn't be so sure that IE won't be recompiled; MS may have stopped developing it, but they probably don't want their browser to be known as "the broken one".) Tverbeek 07:53, 1 August 2005 (UTC)
What's the performance hit from using Rosetta? —Preceding unsigned comment added by 209.240.239.139 ( talk • contribs) 15:11, 15 August 2005
An interesting point that I do not see covered would be "Where is Rosetta located in the system?" Is it embedded in the kernel? Or is it a file? Also, how does the process start? This information, of course, would only increase understanding of how OS X for Intel works.
Further to that, is such information deliberately concealed by Apple (probably for good reason)?
Should Rosetta 2 be incorporated into this article or have an article of its own? Herbfur ( talk) 20:13, 22 June 2020 (UTC)
With this in mind, it seems plausible to think Apple will retain support for Rosetta 2 within the macOS into at least 2023.
I've again removed mention of install-time translation per WP:V ("Any material that needs a source but does not have one may be removed"); "it was mentioned in the video at WWDC 2020" isn't sufficient. There's no mention of this feature at
https://developer.apple.com/documentation/apple_silicon/about_the_rosetta_translation_environment or the
https://developer.apple.com/videos/play/wwdc2020/10214 transcript, so someone would need to specify precisely which video. ...Found it in the keynote.
73.69.184.160 (
talk)
12:21, 21 August 2020 (UTC)