And it is not a source of runtime errors - it's a huge preventer. This is, unfortunately, not the case. We've had bugs go into production at jtv that have bee

And it is not a source of runtime errors - it's a huge preventer. This is, unfortunately, not the case. We've had bugs go into production at jtv that have been caused by a combination of haXe's inadequate type-inference, and the Flash runtime's type-coercion mechanics. For example, I once did this: public static function getSwfArg(name, defaultValue=null) {...} Used elsewhere like this: if(getSwfArg("is_on_site", false)) {...} Unfortunately without further type-hints, if the "is_on_site" swf parameter was not present, getSwfArg would magically return the string "false", instead of the boolean false that was passed in. Ugh! I've spent 6 years doing nothing but Java, and more than that working in various dynamically-typed languages. I'd prefer either of those to what haXe has. Having said that, again, I like the compiler enough that I put up with this stuff - I use haXe for many of my side projects as well as at jtv.