RE: DirectX and Talisman Update (Java JDK 1.2 support)

To quote charles on JDK 1.2 support: "No fucking way!" The Java community is having a hard time digesting JDK 1.1, and while it has important new features (like Beans), it still has that crappy AWT stuff, shitty printing, the list goes on and on. JDK 1.2 has JFC, which we're going to be pissing on at every opportunity. This summer we're going to totally divorce Sun. Apple's announcement yesterday that they will encourage Rhapsody developers to write in Java and call native Rhapsody services was a mere shadow of what we're going to be encouraging developers to do. We'll come out swinging with AFC, with our new Multi-Class File format (for packaging both native code as well as byte codes, saves lots of space), with Java language extensions (peteku/andersh are driving), with very easy-to-use support for calling Win32 DLLs (we demo'd a Petzold app written in Java, complete with message pump, windprocs, etc. - you had to look very close to see that it was Java), with classes for DirectX and DHTML, with Enterprise AFC classes (that's all I can remember off the top of my head). We're really juicing up our JIT compiler -- peteku just checked in function inlining last night, and we've got a P5 instruction scheduler, too. Our latest VM beats all comers (Sun, Netscape, Symantec) in almost every single benchmark. -bens