first off, thanks for the feedback! this is the first feedback I’ve ever gotten for the site really … so that’s very helpful
now, for pack200. there won't be much bickering if I don't discuss it at all ;). kidding of course. I *do* want to please as many people as I can, and thus far I've opened every decision up to the public, but pack200 *might* be one of those things where people are just going to have to suck it up.
pack200 is a great technology, I’ve heard of JARs being TWICE as compressed. and it wouldn’t really be too much of a hassle deployment-wise, since this year everything is being deployed from Java Unlimited itself (so I don’t have to take a week to archive everything later).
the problem with pack200 is that it throws out EVERY previous version of Java. we can’t allow pack200 AND normal JARs, I mean… the pack200 users will have a SIGNIFICANT advantage! plus, not everybody has upgraded to 1.5 to my knowledge, and seeing as Java Unlimited is in the casual games market, it’s a good idea to keep JRE deployment to a minimum.
I dont know. I want to maximize the 4K games’ capabilities and features, but I want I also want to maximize ease of play. in my humble opinion, pack200 shouldn’t be allowed this year because it’s just such a HUGE difference between java versions, we need to wait until Java 5 is as dominant as Java 1.3 and 1.4 is right now.
of course, we could always hold a separate contest specifically for pack200, say… in the summer or something. but as far as the official 4K contest is concerned this winter, you might want to stay comfortable in your 1.4.2 shoes… (to be continued sometime, I’m sure)