When I used to work on Windows computers, I used Ctrl+F4 to close windows. That held true across applications. I've been working on MacOS X now for about two years and the modus operandi for closing windows is Command+W.
Why do I bring this up? Because I have been interested in trying out NetBeans 4.0. I noticed that RC2 now is available for MacOS X.
I finally got around to read about JDNC (http://jdnc.dev.java.net/), to download a copy, run through the demos, look at the .jdnc files, and read some of the documentation (tutorials, article, etc..) I am very impressed! I think JDNC is terrific. I mean its goal is right on target. I believe this is where efforts should be concentrated.
There have been a number of threads and discussions on Java development on macosx.
In the weeks after Eric Raymond's famous open letter to Sun MicroSystems on the topic of open sourcing Java, I took the position of being a strong advocate of this request. Several months have now passed and I've had a change of heart.
I've had the pleasure to work on a Swing application these recent months, and I'd like to share with you one of the main conclusions I've arrive at.
It did take me a little time to gain fluency with the APIs. After all Swing is a fairly large API (over 600 classes). On the other hand, once that fluency is gained, developing in swing works out all right.
With 2604 classes in J2SE v1.4.2_05, one could say that J2SE is a large API. I mean, compared to other APIs, such as dom4j (153 classes) and hibernate (466 classes), J2SE is large.
There's nothing more satisfying than to see a good plant flourish. I believe CSS to be a "good plant." And it's really satisfying to see that it's taken root on the web so very well. I'm sure we all recall a time when browser support was not as good, making publishers hesitant to employ the technology on "production" sites.
The recent news article on Pete Freitag launching javadocs.org (see http://today.java.net/pub/n/javadocs.orglaunch) was of particular interest to me. I must confess, these types of tools strike a chord with me (more on this shortly). It's hard to gauge the general feeling out there in terms of the level of interest in such tools.
My brain has been slowly digesting the concept of code rot, triggered by skimming random articles or blogs that have recently mentioned the term. Code Rot. It's a good word. We've all experienced it. But it's another thing to understand it. What is code rot??
I just read on java.net an abbreviated news bulletin regarding a comment by Sun CEO Scott McNealy stating that Java will not be open-sourced any time soon. As I understand it, the main reason behind this decision was We're trying to understand what problem does it solve. That's a valid argument.