As one of the people behind NodeBox, I'd love to know why you think this is unfortunate. We have been working hard on an application that runs on Windows, Linux and Mac, and a blanket statement like "unfortunately Java" is a bit frustrating.
As graphic designers we are really sensitive to awkward Java applications that look out of place on Mac or Windows. We are trying to find the right look that works on every platform. We discovered that this has more to do with an attention to detail than the underlying technology. As an example, look at a "Mac-like" application iTunes, iPhoto, iCal or Garageband: none of them use the standard aqua buttons in the main interface, instead opting for custom bitmap buttons.
For us, the choices are really down to Qt or Java. We need a solid graphics layer that provides the same results on every platform. Java's 2d graphics does this, and it has native back-ends (Quartz). Also, by using Java, we can speed up a lot of the Python code without resorting to hunting memory bugs in C++.
Lastly, I discovered at Pycon 2009 that Jython really has become a first-class citizen, officially supported by people like Guido. It also does away with the GIL.
I knew the Java argument would come up eventually: I'm surprised it took so long. However, it doesn't come up with people using the software: our users don't realize/care that we use Jython. Instead they're just happy they can use NodeBox on Windows.
As graphic designers we are really sensitive to awkward Java applications that look out of place on Mac or Windows. We are trying to find the right look that works on every platform. We discovered that this has more to do with an attention to detail than the underlying technology. As an example, look at a "Mac-like" application iTunes, iPhoto, iCal or Garageband: none of them use the standard aqua buttons in the main interface, instead opting for custom bitmap buttons.
For us, the choices are really down to Qt or Java. We need a solid graphics layer that provides the same results on every platform. Java's 2d graphics does this, and it has native back-ends (Quartz). Also, by using Java, we can speed up a lot of the Python code without resorting to hunting memory bugs in C++.
Lastly, I discovered at Pycon 2009 that Jython really has become a first-class citizen, officially supported by people like Guido. It also does away with the GIL.
I knew the Java argument would come up eventually: I'm surprised it took so long. However, it doesn't come up with people using the software: our users don't realize/care that we use Jython. Instead they're just happy they can use NodeBox on Windows.