[Interest] Qt on Windows Phone 8
aschmidt at dekaresearch.com
Thu Jun 21 15:44:48 CEST 2012
> * Apple apparently /allows/ interpreters in apps, as long as your app
> doesn't have the capability to download /external/ code to be
> interpreted (as to circumvent the "In-App purchase" - again, an
> "economical reason", not a "technical based one")!
It's *NOT* just an "economic" reason. Apple does not want
uninspected code to show up in the apps that have already
been expected and okayed for use by the users.
Many folks mock the Apple "walled garden" approach, but
so far, it has worked very well to prevent malicious apps
from getting out to users or letting malicious external
forces get malevolent code onto to the iDevices.
From: interest-bounces+aschmidt=dekaresearch.com at qt-project.org [mailto:interest-bounces+aschmidt=dekaresearch.com at qt-project.org] On Behalf Of Till Oliver Knoll
Sent: Thursday, June 21, 2012 8:33 AM
To: Qt Interest
Subject: Re: [Interest] Qt on Windows Phone 8
2012/6/21 Konstantin Tokarev <annulen at yandex.ru>:
> 21.06.2012, 15:05, "Till Oliver Knoll" <till.oliver.knoll at gmail.com>:
>> problem to properly port Qt/QML on the iPhone/iPad (that comes from
>> the App Store rule that "No interpreter allowed" - not specifically
> However, Lua interpreter is allowed.
Yes, true! In fact, I have to revise my previous statements:
* Apple apparently /allows/ interpreters in apps, as long as your app
doesn't have the capability to download /external/ code to be
interpreted (as to circumvent the "In-App purchase" - again, an
"economical reason", not a "technical based one")!
* The reason why I wrongly stated that Apple would disallow
that people had trouble with porting the V8 JS engine (of Qt 5/QML).
But /not/ because that was forbidden per se, but rather because of
Just In Time compilation which apparently does not work/is forbidden
on iOS, due to sandbox restrictions (or so; didn't bother to go into
"If you embed your own interpreter engine (any programming language),
you will have to disable JIT (or any other dynamic executable code
generation), as writing executable code will not work in the app
sandbox on stock OS iOS devices."
So, for Apple basically as long as it is made sure that you pay your
30% to Apple for every buck you earn they don't lock you in into a
specific technology or language (even though the "economical
constraints" do have technical implications, off course).
And I think Microsoft will just follow the same reasoning when it
comes to allowing apps on Windows 8 Mobile (or whatever it will be
called) - or Windows 8 desktop, should there ever be a similar "App
This e-mail and the information, including any attachments, it contains are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message.
Please consider the environment before printing this email.
More information about the Interest