Skip to main content

Aakash?

This was the subject of an email I received from someone I know. The message asked for my review of the Aakash tablet, a low cost tablet which the Indian government in promoting. I replied with a verdict: uninspiring.

My reasons were thus: The processor was pathetic; I cannot expect an ARM running at 366 MHz to provide any reliable computing. My mobile phone runs Android 2.3, and has a 600 MHz processor. Yet, I find it sluggish. To compound the problem is just 256 MB of RAM. I really cannot expect any performance from this tablet. Pathetic configuration is the first thing that ruins a computing experience.

Further, the tablet has no 3G or GPRS, only WiFi (This is set to change in the next release of the tablet, with a better processor and Android 2.3 and GPRS connectivity, but still, I really cannot understand the point of including WiFi over 3G. After all, how many people who are the target audience of the government possess access to WiFi. If they did, why would they buy Aakash over anything else?

The battery is just pathetic, with 2300 mAh, it lasts for just 180 minutes, or 3 hours. In contrast, my laptop lasts me for 6 hours on a fully charged battery, a MacBook lasts for up to 9 hours on battery. If I would design a mobile computing platform, I will definitely design it so that it lasts for a considerable amount of time on battery. It will be pretty useless if it runs out of juice in 3 hours, considering that unplanned load-shedding in non-important villages in India extend for around 18 hours.

The touchscreen is resistive. Frankly, this is the best way to screw up any product today. Everyone loves capacitive touch screens, they are much easier to use, and support multi-touch gestures. Put in a resistive touch screen, and suddenly, you've lost everything people expect nowadays from touchscreens.

Aakash does not retail for $35. It costs INR 2500, which is around $50. The $35 is a subsidised price announced by the Indian government. This means that every time a college student buys the Aakash, the Indian taxpayer spends around $15 to support the purchase. Just to offer a comparison, the amount of the subsidy is approximately the earnings of a "below poverty line" family for a month. A million tablets, that's a lot in subsidy, considering that most students already have access to computers, either in their college labs, or possess their own computers.

While we are discussing students, I cannot see any student write his undergraduate thesis on an Aakash tablet. It does not have a real physical keyboard, and hence is a pain to type upon. So, I wonder, what are the students supposed to do with the Aakash. Most colleges don't have WiFi all over their campus. My own university has very select WiFi hotspots, and they are all secured. Even so, I really don't fancy walking over to the department in the middle of the night to access my email. Well, maybe that's what the government really wants. When internet access is difficult, students will not access it, and will sleep on time. Yes, that's what it's about.

Aakash is made by DataWind, a company based in London. I really cannot fathom why the government has agreed to offer a contract to a company based in London, for a tablet that is sub-standard, and heavily subsidised by the Indian taxpayer, when the money for the subsidy could easily be put to better use (in my humble opinion) supporting a family below the poverty line for a whole month. Moreover, the "Take it or leave it" offer made by the government in a market flooded with Android based tablets will hardly go down well with the people.

Comments

Popular posts from this blog

On Harry Potter and why I dislike the series

There could not be a better time for this post. There could not have been a worse time for this post. Now that the penultimate movie of the series is out, and my facebook wall filled with people who loved the movie. But this is something I really wanted to say, and I shall say it anyway. Harry Potter is pathetic literature. Now, you must be wondering why I say that. There are many reasons. Firstly, the storyline itself is flawed. When a writer sits down to write anything, he/she must set up some essential rules about what is happening. These rules must remain constant irrespective of how many times he/she changes his/her mind. This is so that the readers are allowed to have some sensibility in what they are reading. In the fourth book, Rowling goes ahead and kills Cedric. Then, at the end of the book, the horseless carriages are there again. Nothing special. We all knew that they are horseless. But then comes the fifth book, and BAM, the horses are actually winged beasts that only thos

ERROR_SUCCESS

ERROR_SUCCESS. This macro would be familiar to all those who have done some programming in WIN32. It is the output of the GetLastError() function to check the thread's last error state when no error has occurred. Weird, isn't it? I mean, if it is a success, then why is it marked as an error in the macro? This is one example of a badly made API. APIs are considered bad when programming in them becomes non-intuitive. Software is said to be bad (or said to suck) when it seems counter-intuitive to the user. There is one very simple example of this. Start notepad. Type in any text. Click on close. The message that you see is: This makes no sense to me as a user. Of course, the programmer follows the approach that he creates a temporary file called Untitled , and in that file he allows the user to make all his changes. But how am I, as a user to understand that? A similar disconnect occurs even between two different programmers. That is why it takes a whole lot of effort to make

Elements of a Story: The Whispers

I'm compelled to begin each post with a meta. That way, my blog posts seem less like essays or dissertations, and more like diary entries, or web logs. So here goes... I started this blog a little over a year ago. The main purpose of this blog was to experiment with styles of writing, and find an effective outlet for all the subjects I wish to rant about; saving my classmates the agony of having to listen to them. As I wrote this blog, I've experimented with so many styles, and have received comments claiming that my work is a shameless copy greatly inspired by so-and-so author/work. Fact is that I simply chanced upon that style. I read, so obviously, my work shall reflect the styles of those I admire, but I've worked out so many styles without even knowing that they exist, only to be informed of them later. Recently, I've been struck with the seeming absence of whispers as an element of a story. The more I've thought of the subject, the more I've been convince