Microsoft pushing for 16-core Atom CPUs: something to do with Linux?

According to this article, Microsoft is pestering Intel to produce low-power Atom-based, x86 processors for server machines.

I am wondering why they would force this direction. Do they know server requirements better than Intel? Why do they think that low-power x86 server chips are so important?

I believe the answer comes from the following factors:

• Power efficiency is becoming more and more important in the server room. Intel processors (Microsoft's home turf) have less than stellar watt/performance efficiency but they are the best in raw performance / cores.


• ARM provides the best watt/performance in general computing (far far better than Intel x86) and ARM is seemingly scalable to the server performance range (with multiple cores and coming to 28nm high-performance production processes)


• Microsoft doesn't have a server operating system presence on the ARM architecture. Linux on the other hand runs on ARM, has optimized distributions for ARM SOCs.


• ARM licensees are actively pursuing server chips (Nvidia, Nufront...etc)

If 4-16 core ARM server processors appear in the near future, servers built with them would have superior watt/performance ratios so they may quickly gain acceptance.

These systems would be perfectly served by Linux distributions (Red Hat, Ubuntu, Suse) and Microsoft could not offer anything for them. Linux is already the strongest player in the datacenter and this would grow its market share considerably while reducing the market-share of Windows simultaniously.

Even if Microsoft manages to create a stable Win8 server OS solution with all the required additional Windows sw (database systems, application servers…etc) on ARM in 2-3 years, it will be pretty much too late. They will need to play catch-up with Linux. The Microsoft Win8 solution will have to sell for peanuts to be in the game which would make it very much unprofitable in the short-medium run. Moreover, as x86 server market share goes down, their x86 Windows Server OS profits also go down.

All in all: If ARM processors appear in the market in the near future, Microsoft may face a steep uphill battle in the datacenter. If x86 based Atom server can slow down the onslaught of ARM servers, Microsoft may gain enough time to come up with a Win8/ARM server solution and avoid serious loss of server market-share.

Nvidia Tegra3 launch imminent. Intel, you did this to yourself.

Reading about the likely launch of Tegra3 at Mobile World Congress 2011 and seeing this video, one cannot help wondering how big a mistake Intel made when denied Atom hardware interfaces from Nvidia some time ago. Doing that, it practically forced Nvidia to abandon mobile-x86 solutions and pour all of its resources into Tegra/ARM development.

Nvidia has recently announced its Project Denver effort which also shows how seriously the graphics company wants to transform into an all-out computer technology company shipping mobile, desktop and server processors as well not only graphics solutions.

As a result, Intel will have to face not only AMD in the desktop/server segment but a big-name ARM technologist as well. (And several smaller ones like Nufront)

Tegra3 is not well known yet, but some guesses can be made:

• Quad-core Cortex-A9 symmetric multi processing for generic application code execution


• Likely at least 1Ghz top, possible up to 1.5 Ghz, dynamic frequency scaling and individual core-power-off


• Geforce 8 or 9 level graphics core, likely with high-profile 1080p playback and encoding


• Support for Linux and Android


• Possibly produced on a <40nm process (GlobalFoundries 28nm anyone?)

If Nvidia can produce this on the GlobalFoundries 28nm process (or similar), we can be quite certain that the new SOC will still be viable for smartphones and will be an extremely appealing solution for tablets and Motorola Atrix-like phone/netbook/tablet modular solutions.

It will make Moorestown Atoms a very-very hard sell for Intel in the mobile phone and tablet space since the computing-power advantage of Moorestown is gone and Tegra3 will be much more efficient (being an all-out ARM solution). Android-centered OEMs will most likely go with ARM anyway and if there is a big-name producer like Nvidia with a powerful solution for their premium products, they will certainly pick that up instead of the Intel gear.

And this is only the mobile space. When Project Denver from Nvidia and Nufront start selling ARM based server SOCs, Intel will have to fight a battle in the datacenter which was absolutely home-turf so far.

All of this may not have happened at all (or would have happened years later, giving Moorestown a chance) if Intel had not chosen to deny Nvidia the hardware interfaces for building Ion2. They switched a huge threat and possible cut-throat competition in every computing segment for a very short-term gain in one segment.

Was it worth it Intel?

Motorola Atrix vs the Always Innovating Smart Book

It is not an overstatement that the Motorola Atrix smartphone was one of the bright stars of CES 2011. An often-mentioned, breakthrough feature of the  Atrix is its modularity, namely that it can be placed into a netbook dock which gives it work-time (and battery recharge) and a desktop-like work environment (Linux based).

It is worth mentioning that this concept is not brand new and that a smaller company called Always Innovating (AI) has a similar, even more modular product: the Smart Book.

The main difference between the two products is that the computing core of the Smart Book is only a MID, not a real mobile phone like the Atrix.

The advantages of the Atrix over the Smart Book (SB):

• The computing core of the Atrix is a real, usable mobile phone, not only a MID (IP phone as AI calls it) as with the SB. The Atrix phone is a high-end Android phone with beautiful, high-res screen (comparable to the iPhone4).

• The computing core of the Atrix has 1GB of RAM and a powerful Tegra2 (dual-core Cortex A9) instead of the last gen, slow Cortex-A8 SOC and only 512Mb RAM in the Smart Book.

• Computing core of the Atrix has a built-in 3G modem (with strong HSUPA and HSDPA) while the SB has only wifi radio and requires you to use an external 3G modem to connect to the internet when on-the-go.

The advantages of the Smart Book (SB) over the Atrix:

• Much more modular. The SB has tablet jacket AND keyboard/netbook dock for the tablet jacket, while the Atrix only has a netbook jacket for the phone. The SB's tablet jacket has a capacitive touch interface


• The SB has real a real desktop operating system (Ubuntu) running when in desktop mode while the the Atrix has only Webtop (that only looks like a full blown desktop but it is only a Splashtop-like quick-linux OS, so it is limited to a selection of programs and is not easy to extend with apps).


• The SB has 2 inner USB ports for replaceable 3G modem or storage key which can always ship safely within the netbook dock (no protrusions)


• The SB's netbook dock can be used as an independent bluetooth keyboard


• The SB's tablet screen can be used as a secondary display of a desktop (DisplayLink)


• The SB has a dockable (into the talet) HDMI to USB adapter (DisplayLink)

In order to be the perfect companion, the Atrix needs to:

• Increase its modularity by separating the netbook dock into a tablet and a keyboard stand or at least release a tablet dock as well


• Upgrade the Webtop desktop environment to a real, powerful desktop Linux (aka Ubuntu 10.04) or at least ensure that Ubuntu can also be used in place of Webtop. It is important that the user be able to switch between Android and Ubuntu real time

The Smart Book could be a worthy contender to the Atrix by:

• Upgrading the computing core to a dual-core OMAP4 with 1GB of speedy RAM


• The computing core needs to be a real-word Android mobile phone with a strong HSPA data modem

I believe Motorola is in a better position to make the Atrix a one-stop computing solution but I also root for Always Innovating to make the Smart Book a successful product.

Both products clearly mark the future: modular, mobile computing for everyone.

The case for a new Apache/Google "Java"

I believe it is high-time that Apache and Google created a new, Java-like programming language, platform and VM which can easily accomodate the ports of the Java base libraries, all of the Apache developed Java libraries/applications and the typical, popular open-source libraries like Hibernate.

Java should start off on the same road as LibreOffice under a different name.

The new "Java" language should be sufficiently close to Java that a one-to-one source converter tool can be written for trivial porting of Java libraries. Apache Harmony is a good basis for this but Snoracle patents will have to be worked around.

The platform should be completely modular and compatible with the packaging systems of Linuxes (apt/yum) and other repository based packaging systems, so that self-containing application packaging can be avoided (this is the case now with most Java applications).

While the language should be backward-compatible with Java, it should incorporate most of the new language advancements of .Net, Python and Ruby. Of course only those which don't kill basic Java language features like strong-typing.

The new "Java" platform should have an Apache-led, democratic governing body. Similar to the JCP but without veto rights for anyone.

When the platform matures to 1.0 (if Google backs the project with enough cash, it could be reached quickly, since Harmony is likely a good starting point), Apache and Google should publicly announce that they stop active Java development, freeze all of their Java-based projects until they get ported to the new platform. Google should deprecate Java in the App Engine and thus forcibly move developers to the "new" Java. This migration should be easy/trivial.

This would of course practically kill Java but the new "Java" platform would become much stronger than Java has ever been because of the following:

• Since it would be distributed under the Apache license, it would be very commercial-friendly and appealing to companies. We can expect every sane company moving to the new platform in the medium term especially because:
  
  
  
  • This platform would be truly open and the stewards (Apache/Google and possibly others) respected and trusted (esp. Apache)
  
  
  • Nobody actually believes that Oracle will be a good steward of Java.
  
  
  • Oracle will want to squeeze every last penny of Java (will hurt Java developers/users) without actual development of the platform. Just like they did with Oracle Forms and Reports.
  
  
  
  


• Due to the open-source nature, packaging and modularity of the new platform, all Linuxes would happily include the new platform and this new "Java" would soon become the primary  development language of Linux projects, completely ousting Mono/.NET on the way. Those Linux projects would run on Windows as well so they would strengthen the migration path from Windows to Linux.


• Strong Linux support would bring a substantial developer base to the platform (the open-source developer crowd).


• Google would officially switch to this platform and the success of Android would help its rise considerably.


• Android would bring a substantial developer base (huge number of Android developers)


• Running Android applications on desktops would become possible which doesn't make sense now but it will soon, since a lot of Android apps will be soon rewritten for tablets and thus become eligible for desktop use.


• The new language should become a primary citizen on the LibreOffice platform. Possibly a basis for every new, larger development in LibreOffice.


• When projects like Maven and Ant get frozen on the old Java platform, developer migration will ensue en-mass to the new "Java".

The new platform would quickly dominate the server-side, where Java is the strongest currently and Linux is on the rise. It would also quickly dominate the mobile space due to Android.

It is possible that the new platform would also become successful on the desktop, at least in the enterprise space where a lot of Java desktop applications are deployed. The Linux desktop would be the first, possibly it would be followed by the Windows desktop.

Java in its current form, under the stewardship of Oracle, is destined to slow decline. Only a radical renewal like this could put it firmly back to the map of relevancy.

Revised specifications for the Notion Ink Adam

As the Adam is approaching its public release, some parts of the specification have changed compared to the originally published spec and there is now some information about the target pricing as well. Of course any of it is subject to change. Some of this information is not even corrected on the official Notion Ink website but was posted on their blog.

The bezel of the tablet has been slightly enlarged (as can be seen on the picture):



There will be four base variants of the Adam:

• PixelQi screen, wi-fi


• PixelQi screen, wi-fi, 3G cellular modem


• Ordinary LCD screen, wi-fi


• Ordinary LCD screen, wi-fi, 3G cellular modem

Both the PixelQi and the ordinary LCD screen will have capacitive, multi-touch interface and 1024x600 resolution, anti-glare coating (matte finish). This is especially useful for reading and outdoor use. PixelQi variant is usable in direct, strong sunlight.

There is no info yet on the HSDPA/HSUPA speeds for the 3G cellular modem.

For internal storage, 16 and 32 GB flash will be selectable.

Common specification elements:

• Nvidia Tegra2 System On Chip operating at 1Ghz (dual-core ARM Cortex-A9)


• 1 GB of RAM (DDR2, 667Mhz)


• WLAN 802.11 b/g/n (previously it was not known whether it will have "n" as well)


• Bluetooth 2.1 EDR with A2DP (for stereo bluetooth headsets)


• External loudspeakers (expected to be good quality for enjoyable video playback), external microphone, headphone and microphone jack


• 3.2 Mpixel swivel camera which will be usable for both taking photos and video calls


• 2 normal size USB ports and 1 mini-USB port


• HDMI output


• microSD card slot


• Docking port


• 3-axis accelerometer


• Ambient light sensor and automatic screen backlight adjustment (this will have a big, positive impact on the battery runtime)


• Manual LCD back-light switch (most useful for the PixelQi variant)


• Standalone GPS chip and antennea (with support for A-GPS quick positioning). The Adam will be capable for navigation without 3G network coverage


• Sound volume keys


• Backside trackpad (this is an interesting part, check the videos on Youtube)


• 24 Wh battery (3-cell configuration). Expected runtime is 15 hours for wifi browsing (recently reported on the blog), 140 hours of listening to audio, more than a week standby


• Operating system is Android Froyo (2.2) with a custom, tablet-enhanced user interface

It is not yet known whether the Adam will have a digital compass (for better navigation and augmented reality apps). It has been asked on the Notion Ink blog comments but no confirmation yet. It would be very much logical to have it in a machine with this hardware level but the long-time omission from the specs indicates otherwise.

Target end-user prices are between $400 and $500 for the 4 variants in the US. Their target is to keep even the fully loaded variant below the price of the entry level iPad.

Availability/release of the Adam is not finalized, but the Early Access Program winners (developers) are expected to have their machines shipped around November 15. Public release should happen soon after in order to make the Adam available for the Christmas shopping season.

Sources:

• Notion Ink Blog


• Notion Ink Company Website

DDR2

My dream: Java SE on Android Linux

Although the Oracle - Google Java lawsuit looks ugly, there is a possibility that something good comes out of it: full Java SE appications running on Android.

That would be an awesome success for Oracle since it is by nature (steward of Java) interested in running Java applications in Android devices. Devices shipping with Android (tablets with dual-core ARM processor and 512Mb to 1 GB of RAM) are powerful enough to run full Java applications, even with Swing. Desktop applications are quite common in the enterprise space and would make Android devices very appealing in this segment. Especially in the tablet form factor.

Due to the overwhelming success of Android, Oracle would gain a lot of possible support contracts for Java SE on Android (support contracts are the ones Oracle is usually after)

Oracle should get over the need for controlling where Java SE can go (it is currently not allowed on phones) and remove these restrictions. Most of them don't make any sense anyway.

Google and Oracle should work together to create a flawless SE JVM for Android (the Linux runtime is probably a good basis for that) and make sure that graphical Java programs (Swing) run nicely and feel native on Android. Sun has made a lot of optimizations for ARM Cortex A9 level processors, that work should not be lost.

Synergies between Java and Android are already very strong, this step would correct Google's original mistake of leaving out SE compatibility of Android (I know the reasons but still I think it was a big mistake nontheless).

The biggest mistake Palm has made with WebOS

Palm's WebOS (a Linux variant) based phones have been out for a while but I haven't had the need to consider them until recently (in the form of my Treo 650 broken down).

My Treo 650 was a real workhorse, containing hundreds of contacts, thousands of calendar entries (I use the calendar actively and like to keep entries for a very long time for reference), lots of todos and memos. As a long time Linux/Ubuntu user, I have synchronized and backed up my Treo with JPilot, which is an excellent Linux application. In the past, I have used several Palm devices and I was always able to migrate my complete PIM database with ease between the old device and the new one.

Now that my Treo seems to be dead, I was considering buying a Palm Pre. Researching the Pre, I soon learned that the old synchronization protocol (Hotsync) doesn't work at all with the Pre and there seems to be no way to correctly synchronize the Pre with my Linux desktop. Since I store relatively sensitive information on the Treo, I would never synchronize my PIM database with a cloud service like Google. Thus, Palm's new Synergy sync methods are practically useless for me.

This problem is not only related to the Linux desktop, Windows users are affected as well but they at least have existing third-party options for synchronizing the Pre with Outlook.

Now, this is a real show-stopper for me and lowers the Pre from a trusted Palm device to the level of the average smartphone in my eyes. Palm seems to have lost an avid user since if my workflow is broken anyway, I might as well switch to Android. Android has a much bigger community than WebOS, so there is a bigger chance that I find a well working syncing solution to the Linux desktop.

It is also ironic that although Palm's new WebOS is a Linux device, Palm has decided to break compatibility with the Linux desktop since the only working way between them was HotSync.

It should have been of paramount importance for Palm to ensure compatibility with its own Palm Desktop software and all of the other desktop software which was communicating with Palm devices over HotSync. Currently, Treo owners don't have an easy way to upgrade to the Pre/Pixi since their PIM databases cannot be easily migrated to the new device the way they are used to. As a fair chunk of Treo users were business people, I am sure, most of them are NOT comfortable with their PIM database stored in the cloud. Palm should understand that cloud storage with Synergy - while a good thing - is NOT a replacement for HotSync in a lot of user scenarios.

I believe that Palm's lower-than-expected sales of the Pre and the Pixi can be amounted to this, incompatibility with the old ways and the well-working syncing solutions and desktop tools. Their established Treo/PDA customer base will simply switch to other phones and leave them. This way they loose all of their inherited advantage with this people.

If they want to save the customer base which is still on PalmOS, they should VERY QUICKLY create the HotSync client for WebOS or create a HotSync Synergy plugin and restore compatibility with the Palm Desktop and all of the other desktop software which are still using Hotsync.