This sounds pretty nice. In Lisp, this would be considered a "tree shaker" (mind I don't know how they're plan to use this). Currently, we rely on the Java Mod

This sounds pretty nice. In Lisp, this would be considered a "tree shaker" (mind I don't know how they're plan to use this). Currently, we rely on the Java Module system to make reduced runtimes. It works, but is necessarily coarse. You'd think you'd be able run the application for a "suitable amount of time, and a suitable amount of use cases" and monitor what classes were loaded, etc. and use that information to make the smallest runtime possible. The addition of the sealing mechanism is a bonus, most apps simply don't need to be that configurable and flexible. You could do that analysis once, and update it manually (so you don't have to do it all the time), or have some automated service that you run routinely. I have a simple GUI program, getting ready to distribute. It's 5000 lines of code, and has a couple of windows. Admittedly, it also includes WebKit (which alone can be large), but with all the the distribution is 70M. That's tuned using the module system, so it leaves stuff out. That's "good". Many other cross platform solutions are larger. It would be great for something like this to knock that down to 20M (cough).