It was crashy: some of the external processes like gasp javac, would hang and cause 100% CPU usage indefinitely. Last year I took the same source code, and used windows ports of kzip and others. The results were so bad (as in: not even close ) that I didn’t bother to continue the effort.
It’s really not rocket science… it’s just that you rely on external processes which either do a good or bad job.
Maybe an applet that uses the client’s processing power to generate the jar, instead of the server?
It would be an applet that has one text area for the java code, maybe the target jre, and one button to generate a jar that the user can somehow download from the applet. Possible?
That way that app can be hosted on java4k.com for posterity.
When I used JShrink on one of my files, I nearly fell out of my seat. It reduced my Jar file by 1 KB!! It was enough to put it on J4k, but it was an application.
Yes, but it’s a bog standard one, and probably uses a simple greedy parser. A good zip library will squeeze a few more bytes out. As a quick test I’ve just compressed a group of already fairly well compressed programs I had sitting in my temp directory with both jar and kzip. jar got them down to 90.6% of the original size, and kzip to 88.6% of the original size.