Intel Rolls Out "Beacon Mountain" Android Dev Platform For Atom 126
MojoKid writes "In an effort to coax developers to begin taking Atom seriously as an Android platform, Intel has just released a complete suite of tools that should help ease them into things — especially since it can be used for ARM development as well. It's called Beacon Mountain, named after the highest peak outside of Beacon, New York. As you'd expect, Beacon Mountain supports Jelly Bean (4.2) development, and with this suite, you're provided with a collection of important Intel tools: Hardware Accelerated Execution Manager, Integrated Performance Primitives, Graphics and System Performance Analyzers, Threaded Building Blocks and Software Manager. In addition, Android SDK and NDK, Eclipse and Cygwin third-party tools are included to complete the package."
It already has caught on. (Score:5, Interesting)
Microsoft products are...
Android and Chrome head Sundar Pichai has just revealed that Android has passed the milestone of 900 million activations, up from 400 million in 2012 and 100 million in 2011 (to put that in some perspective Windows Installs is about 1.2Billion). Its an incredibly popular OS that people want, on devices people want. The same is not true for the current version on Windows with its new tablet interface, on current PC's, Which is damaging the whole PC industry....and in context of this article why intel wants to be part of this growing wave of devices.
Won't help with 'to-the-metal' apps (Score:3, Interesting)
Increasingly, the best Android apps will use C++ and assembler, producing binaries that will NOT run only dodgy x86 versions of Android. There is already an issue of the best 'to-the-metal' apps on Android only running on certain ARM tablets, although this is usually down to laziness or excessive caution by the programmers. ARM provides excellent ways to ensure ARM binaries have sufficient support for the minor variations found amongst the most commonly used ARM CPU cores, the main variation being in the area of vector acceleration facilities for floating point code.
The world doesn't need x86 Android. The world doesn't want x86 Android. The world is only subject to x86 Android because Intel (illegally) PAYS third parties to build x86 Android devices. There is no sane commercial reason for any company to use an Intel chip UNLESS Intel turns up with wheel-barrows full of cash and shed loads of free low end x86 parts. Luckily, getting the devices built doesn't help Intel subvert the marketplace, since no-one chooses to buy them. Buying an Intel Android tablet would be like buying a non-cortex ARM based tablet. Sure, they'll both run 'Angry Birds', and other primitive Java only apps. However, no aware person would choose a non-cortex ARM or x86 CPU unless they wanted to be constantly checking the compatibility of Android software (and at least Android ARM binaries CAN be made compatible with non-cortex ARM v7).
We've seen this before, in the early days of Microsoft NT (now, what you call 'Windows'). Microsoft backed 3 or 4 different CPUs, and provided tools for each. In theory, an app could carry binary pay-loads for each type of CPU in the same package. In practice this NEVER happened. Either an app was a general program for a common x86 based PC, or an app was a highly specialised program for a MIPS machine or whatever. Of course, back then the (supposedly) CPU ISA independent .NET initiative did not exist.
Or again, consider the nintendo Wii U. This console was designed for brainless and cheap ports from the Xbox360. The Wii U has CPU and GPU features that can be considered as supersets of the Xbox360, but in reality things are more complex. The Wii U may have more power than the Xbox360, and 'compatible' hardware (same CPU ISA, GPU form same company), but now almost no Xbox360 developer is creating versions of their games for the Wii U. Intel's argument for Android on x86 is like Nintendo's argument for the Wii U- namely that developers from successful platforms will obviously want to port their apps/games across if the process is 'easy' enough.
In the world of software development 'easy enough' is a buzz phrase designed to fool the 'pointy-haired bosses', and it doesn't even do this. The very reason, for instance, that EA no longer codes ANY games for the Wii U is the self-same reason vanishing few good apps will appear for the x86 version of Android. Testing, supporting, and porting just won't be worth the effort. Developers who support Intel KNOW they are uselessly helping to fragment the Android market, AND support a CPU manufacturer that, if successful, will massively raise the cost of x86 Android CPU parts. Intel's mad dream is to drive ARM out of the mobile market, and then to raise the price of their mobile x86 parts back to notebook levels.
Re:It already has caught on. (Score:4, Interesting)
Just because Eclipse is a terrible IDE, that doesn't mean that all IDEs are worse than Visual Studio!
On Windows, just about everyone with any common sense uses Visual Studio because it's basically the only option, and also happens to be the best development environment for C# and Windows-only C++. For Java development, there's a lot more choice, and unfortunately Eclipse has become a defacto standard in a lot of places, despite being one of the worst IDEs out there.
I use Visual Studio daily, and it's good, but it doesn't hold a candle to IntelliJ IDEA, for example. The new "refactorings" that have been added to recent versions of Visual Studio have been in IDEA for a decade. Download the trial edition, and do some serious work with it for a week or two on a large codebase. It'll blow your mind.