Skip to main content

My first blog from my android tablet

Acre Iconia Tab A500
I picked up my Acer Iconia. A500 tablet from BestBuy yesterday. 24hrs later, the screen looks like its been used for 6 months. It's scary how these things keep you captivated. There are thousands of reviews out there, so I am not going to bore you with another "in-depth" review. Here is short and sweet account of my rendezvous with my new found love interest.



First day retrospective
  • For an android user, this should be a treat, the dual core processor makes the ui and apps snappy. The screen is brilliant but it is glossy, so it was very hard for me to use it on the train to and from work. Maxing out the brightness helps a bit.
  • The battery life is simply out of the world. I did not believe the specs and had carried the charger along. And at the end of the day, It still has about 60% of the juice.
  • I dearly miss the Swype keyboard. Although the large screen has larger keys, I got so used to swype that it feels slow typing old-school way. I am going to have to find an alternative very soon.
  • The mail app is awesome. So is the Gmail app, gtalk app. Skype calling on video is sweet. Turning on my laptop to video chat with mom is no longer necessary.
  • There is no memo app. Really. Not that it's a deal breaker. But I am just saying there is NO MEMO app.

Issues found:
  • The browser crashed at times, when the page had multiple flash ads/content
  • YouTube video links open in browser (unlike as in my Galaxy S,  they open in the YouTube app )
  • Games are slightly slower in compatibility view.
It has been a while I have blogged. With the new tab, hopefully i will be motivated to write again.
Labels:

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery
Read More >>

Decorator for Memcache Get/Set in python

I have suggested some time back that you could modularize and stitch together fragments of js and css to spit out in one HTTP connection. That makes the page load faster. I also indicated that there ways to tune them by adding cache-control headers. On the server-side however, you could have a memcache layer on the stitching operation. This saves a lot of Resources (CPU) on your server. I will demonstrate this using a python script I use currently on my site to generate the combined js and css fragments. So My stitching method is like this @memize(region="jscss") def joinAndPut(files, ext): res = files.split("/") o = StringIO.StringIO() for f in res: writeFileTo(o, ext + "/" + f + "." + ext) #writes file out ret = o.getvalue() o.close() return ret; The method joinAndPut is * decorated * by memize. What this means is, all calls to joinAndPut are now wrapped (at runtime) with the logic in memize. All you wa...
Read More >>

Faster webpages with fewer CSS and JS

Its easy, have lesser images, css and js files. I will cover reducing number of images in another post. But If you are like me, You always write js and css in a modular fashion. Grouping functions and classes into smaller files (and Following the DRY rule, Strictly!). But what happens is, when you start writing a page to have these css and js files, you are putting them in muliple link rel=style-sheet or script tags. Your server is being hit by (same) number of HTTP Requests for each page call. At this point, its not the size of files but the number server roundtrips on a page that slows your page down. Yslow shows how many server roundtrips happen for css and js. If you have more than one css call and one js call, You are not using your server well. How do you achieve this? By concatinating them and spitting out the content as one stream. So Lets say I have util.js, blog.js and so.js. If I have a blog template that depends on these three, I would call them in three script tags. Wh...
Read More >>