I'd say their own implementation of the player will use LLVM for accelerated execution of JavaScript to get the necessary performance (they've been contributing to the LLVM project for some time now). Why do I say this? They've submitted a recent (and invalid due to prior art) patent for LLVM IR generation from JavaScript. Don't believe me? See:
Any JavaScript frontend for generating LLVM IR violates this patent (they even mention LLVM IR explicitly here). Ironically there is so much prior art here its not funny (they've essentially repatented in the old UCSD p-System). This patent would cover the generation of bytecode from JavaScript such as already used by Mozilla in their engines. Smells like a future Mozilla-versus-Apple court case.
So much for Apple being high minded in all this. They are simply attempting to corner another market. Makes Adobe look like the good guy again.
Slashdot Mirror
I'd say their own implementation of the player will use LLVM for accelerated execution of JavaScript to get the necessary performance (they've been contributing to the LLVM project for some time now). Why do I say this? They've submitted a recent (and invalid due to prior art) patent for LLVM IR generation from JavaScript. Don't believe me? See:
http://www.faqs.org/patents/app/20100153929
Any JavaScript frontend for generating LLVM IR violates this patent (they even mention LLVM IR explicitly here). Ironically there is so much prior art here its not funny (they've essentially repatented in the old UCSD p-System). This patent would cover the generation of bytecode from JavaScript such as already used by Mozilla in their engines. Smells like a future Mozilla-versus-Apple court case.
So much for Apple being high minded in all this. They are simply attempting to corner another market. Makes Adobe look like the good guy again.