JavaFX 1.2.1 is out, fixes binding leaks and performance

Sun just released the first maintenance update for JavaFX 1.2. This release brings mostly a batch of important javafxc fixes, that I dissect in this blog... Java programmers are used to the fact that compilation of Java source code is a relatively straightforward process, because the Java language has a simple mapping to the Java bytecode. So javac is a trivial compiler, at least in the code generation phase. (Other phases may be more complex – in particular, type-checking has become significantly complex after Java5; but due to erasure, even this basically doesn’t impact code generation.) There haven’t been many code generation bugs over the lifetime of javac, and there are no significant differences in code quality between releases or between javac and other independent compilers (like ECJ). This is different for example from C/C++, where different compilers may produce code of wildly distinct quality. Of course, the performance and correctness of your code can still vary between JVMs, but that would happen in the bytecode-to-native translation, performed by the JIT compiler. So Java compilation is not really different from C/C++, it’s just split in two layers where all the hard work goes in the lower layer of JIT compilation. Now with JavaFX, we are closer to C/C++ compilers than javac was. The JavaFX Script language is not a near-1-to-1 mapping of the Java bytecode spec. Quite the opposite, this language...

Date: September, 09 2009
Url: http://www.java.net/blog/opinali/archive/2009/09/09/javafx-121-out-fixes-binding-leaks-and-performance

Others News