A.F. works on the majority of systems OEM drivers, but that only means 50% or more Deploying Games On The Internet Essay
This essay has been written before on the 'net by shareware professionals (which I'm not, yet), and probably better than I've done it, but the gist of it should remain the same.
Ah, but Cas, you miss one critically important point...
I'm relying on everyone getting a JRE to play someone else's game, and then I can distribute smaller downloads than even you can with JET (you quote the JAR as being as much as 4Mb compared to JET's 5MB - I choose to see that as "wow; a 1Mb saving"
), and rest assured that most people already have the JRE.
Which is why I'll keep telling people that, since AF was written in Java, it "works better and you can get higher scores - but don't tell anyone" if you play it on a JRE
One of the advantages of the glacially slow pace of java releases (1.1, 1.2, 1.3 and 1.4) is that client penetration (oo-er!) is cumulative (OO-ER!), perhaps 75% so. So, we just need a few great java games to get those JRE's deployed, and we're away. When asking friends and family to alpha test my game, I find a lot of them are running windows and already have a JRE that can run quite a lot of stuff (assuming they grabbed the VM updates before MS was forced to stop distributing them to people who didn't have the latest VM already). As long as my game runs at all, they happily go and get a real jre.
I suspect this is because of the aforementioned video card drivers situation. If you are an NV user, then you gave up complaining about large and frequent and ESSENTIAL downloads years ago - every game-playing NV owner knows that you get those detonator updates sooner than ASAP, ESPECIALLY if you have any game problems (and you keep the old downloads, because you soon get used to having to downgrade to get half your apps to start working again