What if you have to download only the first level to start playing? The next level is downloaded in background. Maybe people wouldn't even download the whole game because some developers have said that most people don't even get half-way through their games.

Java is not the problem, Dalvik is. Hotspot is faster but it wasn't implemented at Google so...

You really shouldn't be using C or C++ for user facing applications, unless you're doing Battlefield or something like that. You better be worrying about features than memory management and such.

Android and JavaME are the biggest mobile platforms today so java actually is the biggest winner in tablets, phones, tv cable/over the air boxes, bluray, etc.

Java + SWT is great for the desktop. The best portable runtime environment with native look and feel. What more do you want on top of that?

Isn't there a nanofoot, imperial units users?

No, that means that virtual machines could and did dominate mobile platforms since the start of mobile computing in cellphones and things like that.

In the corporate world, the majority of programmers must use hardware provided by the company that follows strict guidelines about what can be used and that includes Windows-only for the most part. The majority of production deployments are on Linux machines, so there you have a heterogeneous environment where write-once, run-anywhere is necessary.

From the JSR-139-CLDC (http://jcp.org/en/jsr/detail?id=139), hardware requirement: at least 32 kb of volatile memory. What were you saying about computing power catching up something again?

Then you lose the advantage of not having to upload a file if someone uploaded the same file before. If your files are too sensitive to be anywhere else besides your computer, just don't put them anywhere else!

These days, I'm pretty sure the JIT will do a much better job of cache optimization than any C programmer on a real world application. Anyway, real time JVMs are not about raw performance, they are about predictability and are used in very specific domains so I don't think it applies to smooth animations in desktop programs, as long as the OS and hardware is taking care of these, I couldn't care less which language will call them. But yeah, I'm saying Java is better than something I've never worked with, but I know it's implemented and used from C++, so I'll continue to stand against it because that's not the language I'd choose/recommend to develop desktop programs.

GC is run concurrently, unless your program is using all available memory, there is not lockup, I've only experienced it when the application is on the verge to throw an OutOfMemoryError. If the OS is drawing the UI there is no sense in saying Qt is faster than SWT. I've never worked on Qt but the fact it's implemented in C++ is enough to dismiss it.

I think you didn't read what I posted, SWT (http://eclipse.org/swt/) delegates to the Operating System all drawing operations. You may be confusing it with Swing which draws everything on its own. So yes, it can do SMOOTH animations and anything else the OS can draw. People who call java devs fanboys simply doesn't know Java technically enough to criticize it and believe any BS people keep spreading about it, it's the most used platform in the world for reason.

Java+SWT is miles better.

Language is not a good metric because English was chosen mainly because it's a very straightforward language and the US came up in the best position possible after world wars. Chinese is too complex and time consuming to learn.