posted Mar 2, 2011, 6:11 PM by Irwan Chandra
Shockingly enough, Apple found plenty of things to tweak and update on
its spectacularly successful iPad. Alright, so the screen resolution
didn't improve and we didn't get that ultra-speedy Thunderbolt connector
on board, but the iPad 2
is thinner and lighter while somehow becoming more powerful -- a 1GHz
dual-core Apple A5 SOC lurks within. Check out our full breakdown of the
key spec differences in the chart after the break. It's great fun, we
promise!
P.S. - While you're poring over these stats, don't forget that Apple's decided to slap a $100 price cut on the original iPads, making them eminently more desirable today than they were yesterday.
|
iPad
 |
iPad 2
 |
| Display |
9.7-inch
LED-backlit IPS LCD |
9.7-inch
LED-backlit IPS LCD |
| Resolution |
1024 x 768 |
1024 x 768 |
| Processor |
1GHz Apple A4 |
1GHz dual-core Apple A5 |
| Graphics |
PowerVR SGX 535 |
? |
| Memory |
256MB RAM |
? |
| Storage |
16GB / 32GB / 64GB |
16GB / 32GB / 64GB |
| Front camera |
none |
VGA |
| Rear camera |
none |
720p |
| Cellular radio |
EDGE plus triband HSPA |
EDGE plus quadband HSPA or
CDMA / EV-DO Rev. A |
| WiFi |
802.11a/b/g/n |
802.11a/b/g/n |
| Bluetooth |
2.1 + EDR |
2.1 + EDR |
| Accelerometer |
3-axis |
3-axis |
| Gyroscope |
No |
3-axis |
| Thickness |
13.4mm |
8.8mm |
| Weight |
680g (WiFi),
730g (WiFi + 3G) |
601g (WiFi),
607g (Verizon),
613g (AT&T) |
|
posted Feb 11, 2011, 9:21 PM by Irwan Chandra
Well, it looks like Intel's $700 million problem with its Series 6 Cougar Point
chipsets is now one step closer to a resolution -- the company has just
announced that the fully remedied B3 revision of the chipset will start
shipping out on February 14th. That will bring with it an updated BIOS,
full pin compatibility with the previous B2 chipset and, most
importantly, a "minor metal layer change" that promises to improve
"lifetime wear out with no changes to functionality or design
specifications" -- in other words, a fix for that rogue transistor affecting SATA ports. Hit up the source link below for Intel's official notice (in PDF form). |
posted Feb 9, 2011, 8:53 PM by Irwan Chandra
HP TouchPad vs. iPad vs. Xoom vs. PlayBook: the tale of the tape
At last, the webOS-empowered TouchPad,
HP's answer to the growing tablet market. And make no mistake, it's
coming in with guns blazing -- specs-wise, the slate stands up pretty
well to the competition currently in play (e.g. iPad) and the other up-and-comers not quite out the gate (e.g. Motorola Xoom and BlackBerry PlayBook).
Stacked side-by-side, it's clear Apple's entry is lacking a bit in both
memory (256MB vs. 1GB for everyone else) and front-facing camera -- not
that we expect that to be the case for all of 2011.
When it all comes down to it, what'll set these slates apart will be
the platforms and software themselves -- should make for an interesting
summer, no? In the meantime, for the nitty-gritty on technical
specifications, venture past the break.
|
HP
TouchPad
 |
Apple
iPad
 |
Motorola
Xoom
|
BlackBerry PlayBook

|
| Platform |
webOS 3.0 |
iOS 4.2.1 |
Android 3.0 |
BB Tablet OS (QNX) |
| Processor |
1.2GHz Qualcomm Snapdragon
dual-CPU APQ8060 |
1GHz Apple A4, PowerVR SGX 535 GPU |
1GHz NVIDIA
Tegra 2 |
1GHz Cortex-A9 dual-core |
| Display |
9.7-inch |
9.7-inch
LED-backlit
IPS LCD |
10.1-inch |
7-inch LCD |
| Resolution |
1024 x 768 |
1024 x 768 |
1280 x 800 |
1024 x 600 |
| Memory |
1GB RAM |
256MB DRAM |
1GB DDR2 RAM |
1GB RAM |
| Storage |
16GB / 32GB |
16GB / 32GB / 64GB |
32GB |
16GB / 32GB / 64GB |
| Front camera |
1.3 megapixel |
none |
2 megapixel |
3 megapixel |
| Rear camera |
none |
none |
5 megapixel with
4x digital zoom, AF, dual-LED flash,
720p 30fps video |
5 megapixel,
720p video |
| Cellular radio |
"3G and 4G variants" |
UMTS / HSDPA /
GSM / EDGE |
EVDO Rev. A |
3G and 4G |
| WiFi |
802.11b/g/n |
802.11a/b/g/n |
802.11b/g/n |
802.11a/b/g/n |
| Bluetooth |
2.1 + EDR |
2.1 + EDR |
2.1 + EDR |
2.1 + EDR |
| Gyroscope |
Yes |
No |
Yes |
-- |
| Accelerometer |
Yes |
3-axis |
3-axis |
Yes |
| Battery capacity |
6,300 mAh |
6,600 mAH (approx.) |
-- |
5,300 mAH |
| Weight |
740g |
680g (WiFI),
730g (WiFi + 3G) |
730g |
400g | |
posted Oct 14, 2009, 11:16 PM by Iwan Setiawan
[
updated Feb 5, 2011, 2:38 AM
]
Research In Motion's BlackBerry WebWorks Application Platform lets developers use standard Web tools to create applications that work like native programs on RIM's smartphones and PlayBook tablets,company officials said Thursday. WebWorks, a rebranded version of the BlackBerry Widgets development platform that now uses the WebKit Web rendering engine, was released last September at the BlackBerry Developer Conference in San Francisco. On Thursday, RIM returned to San Francisco to give more details about WebWorks, which has been made open source and is available through the open-source development site GitHub. WebWorks is RIM's first application environment for both smartphones and the PlayBook tablet, which is scheduled to go on sale by the end of March. A beta version of the WebWorks SDK (Software Development Kit) for Tablet OS was introduced last month.
RIM rebranded Widgets to emphasize that it can be used to create entire applications instead of just the small on-screen tools usually associated with widget platforms, said Christopher Smith, senior director of research and development for the BlackBerry Development Platform. "A WebWorks application is a complete application. It has full access to all the native methods on the device. All of the data, all of the services," Smith said. All the security tools and policies on the BlackBerry platform also apply to that app, he said. "Under the hood, we are actually wrapping the Web engine in a native container," Smith said. For BlackBerry smartphones, that wrapper is Java, and for the upcoming PlayBook, it is based on Adobe Flash and Air, he said. With WebWorks, developers can program in HTML5, CSS and JavaScript and create applications that are far richer than typical Web-based offerings, said Jeff Jackson, senior vice president of software at RIM. It's hard to tell the difference between Web and native applications based on appearance or capability, Jackson said. At the event, RIM demonstrated multimedia applications on the PlayBook that were written with the standard Web tools, such as an animation program written entirely in CSS. The company offers WebWorks in addition to its native BlackBerry development environment because many mobile developers don't want to learn new programming tools to write apps for each vendor's platform, Smith said. James Pearce, senior director of developer relations at framework vendor Sencha, agreed with that view and said Web-based tools are a good common denominator. "The Web is a crazy thing to bet against," Pearce said. Using standard Web-based technologies is a smart strategy for RIM, which is unlikely to attract the kind of following that the iPhone and Android platforms have built up among developers, said IDC analyst Will Stofega. It lowers the hurdles to getting into BlackBerry development, which could encourage more developers to write for BlackBerry phones and the PlayBook, he said. There are more than 19,000 applications in the BlackBerry App World store now, and about 35 million mobile users have downloaded apps so far, with a current rate of about 2 million downloads per day, Smith said. But that pales in comparison to Apple's iPhone App Store, which has more than 300,000 apps available, and the Android Market, which app tracking company AndroLib has estimated at about 200,000. The iPhone App Store recently celebrated its 10 billionth download. AndroLib recently estimated the Android Market has had 2.5 billion downloads. |
posted Oct 14, 2009, 11:11 PM by Iwan Setiawan
[
updated Feb 5, 2011, 2:37 AM
]
There are more than a few critics of cloud computing, even at PCWorld; I'm probably one of them. But I've been turning over in my mind different perspectives on the cloud. I've tried to set aside the views of the IT executive, who seems to dominate the debate. As far as computer-illiterate end-users are concerned, cloud computing offers many benefits. For example, have you ever lost a file or an update to a document, because you didn't save it before a crash happened? Instead, I've been thinking about what it offers lowly end-users, or for programmers who create the software. What does cloud computing mean for the rest of us?
With an online office suite like Google Docs, it's impossible to lose work. Files are automatically saved every few seconds. There's even revisioning, meaning that you can step back to a file when it was in a previous state. Google Docs isn't alone in offering this. Cloud file storage service Dropbox lets you revert to a previous version of your files, too. The best part is that cloud services don't even require users to understand what "saving" is. There's no longer a need to understand file systems, ushering in a level of simplicity computer engineers have been searching for since the personal computer was invented. Cloud computing offers more permanence for your files than desktop computing. Give yourself a few minutes to think about that. CDs degrade over time. Hard disks crash. But no file will ever disappear from the cloud unless you choose to delete it. Sure, a cloud provider can go bust. But online providers usually give you ample warning to get your data off their service if that kind of thing happens. And, try as I might, I really can't see a company like Google going under anytime soon. How about looking at cloud computing from a programmer's point of view? For a programmer, cloud computing offers something that's been desired for years--the ability to create software that's operating system independent. If you manage to make your app work in Firefox and Chrome running on Windows, then in all likelihood, it will work well on Mac and Linux computers too. Mobile computing devices are also invited to the party, or at least contemporary devices that have the power to run such apps.
Even if a few tweaks are necessary, they'll be nothing like the complexity of recoding applications for every different platform. How about looking at the cloud from a worker's point of view? The biggest boon here is that if a file is stored in the cloud, it will always be available. In other words, if you need that updated spreadsheet from John, there's no need to nag him to send it to you by e-mail. You can just grab the file from the cloud, even if he's still working on it. In suites like Google Docs, you could even open the file, open the chat component, and speak to him as he's editing. IT managers complain about cloud security issues, but what about the security benefits? For starters, cloud computing means there's only ever a central, single version of each file. There will never be versions of potentially confidential files stored on laptops or USB memory sticks, or just about anywhere somebody needed to edit it (maybe even--horror!--on Internet café computers). Additionally, all documents are located in one location, so managers can see at a glance what's going on. John from Accounts might have told you he spent all last night working on the spreadshee,t but now you can see whether that's true and what changes he's made, because the cloud is excellent at tracking revisions and edits. This and other thought exercises indicate the biggest problem facing the cloud is a lack of usage scenarios. At the moment software companies are throwing their cloud products at us and concentrating on making them better, rather than telling us how they can be used. For cloud apps there's often no tried and trusted path as there is with, say, Microsoft Office, which everybody knows offers clearly identified business benefits.
It's down to education. Cloud vendors should spend less time telling us about all the great new features, and spend more time showing their products in real-life situations. Only then are we going to get into the cloud computing mindset. |
|