That really helps maintain my js files. I can be certain that there are no typos in property names, no methods being called with the wrong number of parameters or types. While at the same time still allowing the freedom of a dynamic language in places I deem necessary.

If you can afford to start a new project, and follow the rules specified by the compiler, your javascript code will be much more solid. As for the deleted methods you mentioned, you can mark a method as @extern which will make sure that the method is exported even if not used

Recently I’ve met with both, YUI and Google closure (GC). I tested them on large project, with many complex js files. YUI was faster than GC, but compressed files were bigger than with GC. You allready know that. I’m trying to perform advance compression with GC, but I somehow can’t. The problem is in complexed prototype functions in js. My ant script makes one big js file, with all js code, and then compression is performed on this file. GC says that prototype functions are not defined. They should be treated as defined, because they are all in same file.. I think Did you have any similar problems? Personally I prefer using YUI.

Greetings, Grincho