Intel XDK: An HTML5 development IDE
software.intel.com
software.intel.com
I certainly won't build and distribute mobile apps with whatever obscure (and non-removable according to ToS) "security features" Intel has decided to bundle with the runtime e.g. to comply with arbitrary requests by various rogue government agencies.
If they want us to build HTML5 apps for their own sake (Intel's, they want to fight back against native ARM binaries), they'll have to try harder. Make it Open Source and ask a lawyer who hasn't been stuck in corporate litigation and patenting stuff for several decades to write a modern license (or use the LGPL/BSD/MIT license...).
How will the ToS hinder me from doing so?
Furthermore, they want the right to disable access to some content somehow if they think it is illegal (i.e. they have rights to arbitrary censorship of content and apparently also some mechanism built into the runtime to enforce it). Am I going to distribute or even sell stuff to users that Intel can disable any time they like? Certainly not.
If they wanted a license that puts off developers who have plenty of choices nowdays, they succeeded.
I tried AppMobi early on but as a developer I much prefer something open like PhoneGap, even if (or because) I have to glue the pieces together by myself. I don't really see the demographic that knows how to develop an HTML5 web application but prefers a closed black-box environment for putting together the mobile app.
The AppMobi XDK was pretty slick though. But from the announcement it seems like they pretty much tore it down and started over from scratch.
These days I hold higher hopes for real convert-to-native tools, that actually translates HTML5 (f.ex. the canvas API) to native code.
I should really get a cross-platform effort for Ejecta going. We have CocoonJS and Intel's XDK, but afaik there's no Open Source alternative right now.
[1] http://impactjs.com/ejecta
[2] http://www.html5dev-software.intel.com/amdocs/readmes/ios.ap...
In the standard Intel style (whitepapers, etc), trademarks to other companies are designated with an asterisk and a footnote to the effect of "These are trademarks from companies other than Intel. They own the rights to the name, and not us"
How selfless of them ;)
Intel mistakenly believe that they'll have an easier time by forcing ARM to compete at full speed, which is brilliantly ignorant of history. The very first ARM outperformed contemporary x86s at computation, and just happened to be low power, it's that they've been diverted off into low power as their reason for existing for 20 years.
ARM can, and will, redefine their instruction set dramatically to suit their needs at any time, so while the x86 world is stuck with x86 the mobile world has been through several major changes to the ARM ISA since just the original iPhone.
The Intel PR has persistently been saying "but our next one" for the last few years, and each time it's gone nowhere. They are merely performing the role of a stick device makers can hit ARM with to control prices though, but seem oblivious to this.
Could be really handy for making quick apps for conferences or hi-fi prototypes imo. Particularly the cross platform build system - seems really easy.
Products likes these are what give HTML5 a bad name.
Seems fairly permissive, but has provisions to do with de-compiling anything distributed in binary form so it looks fairly mixed.
This may though just be due to use of some legacy, licensed library somewhere rather than deliberately restrictive licensing. I haven't looked closely at what comes with XDK so I'm not sure what components are used.
Intel, I won't be using it for my money making business. This corporate license thing is so 1990's.
Get with GPL alfaro. You will create way more wealth for the planet that way.
The XDK operates identically on all three platforms, one of the reasons for using node-webkit to create the app.