Re:There has been some good alternatives[reformat] (Score 1)

Yawn. The 'Java is slow, obese and heavy' arguments are poor, out of date and largely inaccurate. Java's popularity on mobile phones suggests it is hardly a performance bottleneck, nor is it too demanding for memory.

I understand you argument, but it sure doesn't apply to phones. Maybe for a simple Java business application, but thats about it.

Find one book, one article about making apps on j2me that doesn't explain how to use obfuscation. Thats not because of all the pirates trying to steal your code, its because Java is big.

In order to make a sophisticated app, you basically have to throw out everything you have come to love about Java to make it work on a phone, namely OO....

Its not the amount of code thats the problem, that's inheirent in any language, clearly. It's the fact that adding classes, or doing anything that the language is built for or suggests you do costs alot.

The Jar footprint and class size comes straight from how many methods, variables, extends, implements, packages, etc.. You would crazy to try to run an app on a phone that have tons of getters and setters - classloader loads that and then whoop, there went 80% of your memory.

For sophisticated apps, this makes Java on a phone is basically procedural code, large case statements, public variables for direct access and maybe 3 or 4 classes tops. At that point, I have a hard time calling it Java, but also at that point, its not obese.

Its popular on phones because there are 2 options, that or BREW.