Saturday, November 26, 2011

Android programming - Eclipse problem solved

I have been programming on Android and iphone. The iphone is a joy to use but hard to program. The android phone? relative easy to program, but the hardware sucks in lots of ways. The AVD (android virtual device) is outrageously slow. My phone is way too sensitive, the bottom row of buttons are way too unresponsive. The rotation is way too sensitive. If I didn't have an iphone to compare, I wouldn't think my Android phone suck so much.

The android has more users, and development on it is free , Java is much easier to program than Objective-C IMHO. Platforms come and go, I took a graduate course to program the Palm a decade ago.

I do most of my android development on Windows. (I should really start doing android dev on my mac) Windows sucks! it takes 5-10 minutes to boot, and at least 3 minutes to recover from hibernate. Worthless Windows! The Apple wake up right away.

To develop for Android, we'd use Eclipse. I have been Google Web Toolkit. Eclipse was taking over 10 minutes to start. The Android AVD take another 5 minutes to show up. Android programming had been painfully slow. I only have a couple hours a day to write hobby code. I can't lose 35 minutes, just to get Eclipse warmed up. Windows = ALWAYS sluggish, Apple = always fast (some beach ball spinning, but tolerable)

Nope, it was not an INI file, it was not a problem of not having enough memory to it. I had 8 Gigs of memory! (unthinkable just a few years ago)

It turns out there are tens of thousands of temp files left by GWT Eclipse plugin. There were over 9 Gigs of garbage in my Temp directory. It took 30 minutes to delete them. How dare you Google, leave 9 gigs of junk around?

The problem is documented here.

Now Eclipse start right away, and I can do some programming.

0 comments: