Filed under: geek

The Acer Iconia Tab is kinda hot!

I just discovered this thing made by Acer called the Iconia Tab W500 and I think I need one. It's basically a full tablet PC with a keyboard dock, but deep inside it's like a geeky fantasy machine! I started looking at the specs and realized that though it's obvious competitor is the iPad, it's performance is actually pretty close to the MacBook Air. Of course it doesn't run any fancy Apple OS, but AMD support in Linux seems to be alright, and it might even make a good Google ChromeOS guinea pig. I spent several hours looking around at benchmarks so I'm now inclined to explain my findings to you. Sit down, this could take a while.

Basics

  iPad2 Wifi+4G 32GB Acer Iconia Tab W500-BZ467 MacBook Air low-end
price $729 $549 $999
screen 9.7” multitouch 10.1” multitouch 11.6”
resolution 1024x768 1280x800 1366x768
height 9.5” 10.83” 11.8”
width 7.31” 7.48” 7.56”
thickness 0.34” 0.77” 0.68”
weight 1.34lbs 3.5lbs 2.3lbs
battery 6930mAh 3260mAh 4500mAh

It's no surprise the Acer looks pretty chunky compared to the anorexic Apple offerings. It's got a slightly larger screen than the iPad, but twice the weight which is surprising considering it's smaller battery. The keyboard might be included, but I don't know.

Connectivity

  iPad2 Wifi+4G 32GB Acer Iconia Tab W500-BZ467 MacBook Air low-end
wireless a/b/g/n b/g/n a/b/g/n
bluetooth 2.1+EDR --- 2.1+EDR
3G AT&T or Verizon --- ---
ethernet --- RJ45 $
hdmi $ yes $
usb --- 4 USB 2.0 2 USB 2.0

Strangely the Iconia lacks a Bluetooth connection. There's room for a Bluetooth dongle in one of it's 4 USB 2.0 ports, but it won't need one for ethernet or HDMI as these are built in. You can't get it with 3G yet, but who wants to sign another contract anyway?

Technical

  iPad2 Wifi+4G 32GB Acer Iconia Tab W500-BZ467 MacBook Air low-end
cpu 1ghz dual-core ARM 32bit 1ghz dual-core AMD x86 64bit 1.4ghz dual-core Core 2 Duo x86 64bit
gpu PowerVR Series 5XT Evergreen cores (roughly equivalent to  Radeon HD 4330) NVidia GeForce 320M
gpu cores 2 80 32
gpu clock 200mhz 280mhz 450MHz
direct x 9 11 10.1
memory 512MB DDR2-1066 2gb DDR3-1333 2gb DDR3-1066
storage 32GB 32GB 64GB

This is where it gets interesting, but kinda complicated. See, computers today are coalecing into just a handful of chips. The MacBook Air has a graphics chip made by Nvidia soldered to it's logic board along with a dual-core Intel CPU which is pretty old-fashioned. The iPad and Iconia however use what's called a "system on a chip" which combines the GPU and CPU among other things into a single chip. Apple went one step further with their A5 chip and threw some RAM right on top to make a nice little silicon sandwich called a "platform on platform".

But here's the thing; Apple didn't design either the CPU or the GPUs in the iPad. The two CPU cores are licensed from ARM who design low-power 32bit "reduced instruction set" chips. These chips aren't as powerful as the x86 chips in your desktop, but they sip electricity so they can be found in most handhelds. The graphics cores—which Apple claims are 9x faster than the original iPad—are licensed from PowerVR who's designs also powered the Sega Dreamcast and Nintendo Wii. Similar GPUs were licensed by Intel to provide integrated graphics for the original Atom platform. These were so bad that Nvidia developed the supplementary Ion graphics chipset to boost performance

The Iconia's chip is a completely different story. It was developed by Intel competitor AMD following their merger with Nvidia's biggest rival ATI. AMD's x86 CPUs gave Intel a run for their money as some of the first viable 64bit chips on the market, but Intel chips generally outperform their more affordable AMD alternatives. ATI's graphics cards on the otherhand have stayed neck and neck with the performance of Nvidia, and often for cheaper. When AMD bought ATI, Intel was starting to sell their onboard graphics chips (despite poor performance) hand-in-hand with their popular CPUs. It was clear that AMD/ATI would need to combine forces to compete.

This year AMD released the Fusion platform; a chip which combines two 1Ghz 64bit CPUs similar to the Atom chips in most netbooks, with 80 Evergreen GPU cores as found in the mid-low range Radeon HD 4330 graphics cards. Having these systems living on the same chip makes for massive power savings as well as a cheaper system to build overall. When benchmarked against an Intel i5 with Intel's GMA HD on-board graphics (similar to the chipset in a 13" MacBook Pro) Fusion sometimes doubled framerate performance in 3D games. Compared to the cheaper Atom chips they compete directly with, Fusion dominates when it comes to graphics.

Now I'm not trying to say that the Iconia is faster than the MacBook Air. In CPU intensive tasks Fusion struggles to equal similarly priced Atom+Ion systems, but when it comes to graphics the Iconia isn't far behind. It also has high frequency DDR3 memory, and a solid state drive to back it up.

Peripherals

  iPad2 Wifi+4G 32GB Acer Iconia Tab W500-BZ467 MacBook Air low-end
keyboard $ yes yes
front facing camera vga 1.3mp yes
rear facing camera 720p 1.3mp ---
memory card --- MMC/SD  
gps yes --- ---
digital compass yes --- ---
gyro yes --- ---
accelerometer yes --- ---
ambient light sensor yes --- yes

Last are the bells and whistles. The keyboard looks good especially if you love nub pointers, and a memory card slot is always welcome. The Iconia has both front and rear cameras, but lacks the location and positioning sensors that are needed so badly for maps and games. GPS is often included with cellular radios, so maybe if they make a 3G version, but something tells me I won't see a compass or accelerometer anytime soon.

So, for nearly $200 less than an iPad you can have a full tablet PC that outperforms most netbooks. I'm using an Asus EeePC with an Atom N550 Ion chipset as my daily driver. I've had it less than a year, but with all the trouble that Nvidia's drivers give me in Ubuntu I'm ready to get rid of it. The Iconia might just be my next PC.

WebKit's Drama of Broken Image Alternative Text

Any web developer worth his salt knows you're supposed to put an "alt" attribute on your images. 

What's an alt attribute you ask? Well, imagine you're blind, or maybe your connection is slow, or you just hate looking at images. In an HTML page,  an <img> tag's alt attribute tells the browser what the image means when the image can't be seen. 

<img src='/images/lolcat1.jpeg' alt='a cat asking if it can haz a cheezburger'>

Screen reader software can read the value of the attribute aloud to a sight impaired person. 

The thing about images is that they are separate files from the web pages they are displayed in. Everyone's familiar with the broken image icon that appears when an image fails to load or has been moved. You might think that if the <img> tag had an alt attribute that would be a perfect opportunity to use it. After all some web developer went to the trouble of putting it there why not go ahead and display it? Firefox and Opera do just that. 

Of course Internet Explorer doesn't (no shock there) but surprisingly neither does Safari, or Chrome. These browsers ignore the alt attribute and just display the broken image icon. If all the images on the web suddenly disappeared, blind people would still know what the images were, but users of IE, Safari, and Chrome would be left in the dark. 

By now I'm sure you're on the edge of your seat and who can blame you? This is important stuff! Many people have reported this issue as a bug in Chromium (the open source project behind Google Chrome) since as far back as 2008. "Firefox and Opera do it right!" they cry. "Why do we spend hours optimising our code for situations like this, only to find it's all a complete waste of time?" But the bug's owners simply pass the buck, saying the bug is in WebKit, (the opensource project behind the software that powers both Chromium and Safari... stay with me now) and has been there since 2005! And I thought I was bad at closing bugs!

Those of you involved in web technologies probably already suspect there is some pedantic debate over some minute detail at the heart of this and BOY IS THERE EVER! It seems people in the Chromium camp can't decide whether the alt attribute should be displayed or the similar title attribute (the attribute responsible for the little tooltip text that pops up under your cursor from time to time). 

Meanwhile at WebKit they are struggling to understand what everyone's getting on about. Back in 2006 a guy named Hixie offered the spec he did for Mozilla on the subject, and the WebKit developers thought about it for two more years. Then in 2009 OmniGroup (another browser maker that uses WebKit, you're still reading this?) provided an actual fix to the bug which they had patched for their OmniWeb browser. All that remained was for WebKit developers to apply the patch, and all would be solved!

They talked about it some more. "This is solely for the (questionable) benefit of sighted users" said one. "I know that I generally don't want any content that's normally invisible to suddenly become visible when images get lost [even when that content was meant to be visible when the images aren't visible]" chimed in another. Again some external links were shared where people outside of WebKit said what everyone inside of WebKit seemed to have such a hard time understanding "The reader of the page frankly couldn't care less if the author has made a mistake and the page is not completely available. The reader wants the information." Still they were not convinced. 

The main concern seems to be that if an <img> tag doesn't have specific dimensions the alternate text might stretch the image's box wider than it should be. This would be catastrophic for sites like the Internet Archive (I don't know what that site is either, but it's really important to the WebKit devs) where they apparently lose images all the time and do not care what they were supposed to be whatsoever. Of course, the broken image icon is just as likely to be too small, but *that's* okay. The developer who provided the alt attribute might also provide a width which would keep their page looking fine. But all this just seems to be too big of a choice for the poor WebKit team, and as of last November they have fallen silent on the issue. 

I would like to see this fixed, mainly because I don't feel like opening Photoshop to make a little pencil icon right now, so I'd like my <img> tag to just say "edit" instead of the same icon as the "delete" tag right next to it which could say "delete" just like the alt attribute tells it to. Maybe I should have just replaced the <img> tag with text for now and gone on with my life. But I noticed that just yesterday some Chrome users decided to get noisy about this issue. This is the kind of crap that web developers have put up with since the web was born, but this is a new day dammit! This is HTML5, this is freakin' Web3.0! We do not want debates about what would maintain the status quo. We want progress! So I'm jumping on this bandwagon, and I will see this behavior standardized if it means forking the whole damned WebKit project! I've had it with engineers that can't make a fucking decision. Shit or get off the pot WebKit.
1 of 1
Posterous theme by Cory Watilo