About a year ago, I jumped on the Mac OS X bandwagon, threw my resources into a TiBook and later into a nifty desktop, and thought I was quite trendy. About 4 months ago, I got annoyed at all the things that I was used to acting just slightly off, and went back to my trusty PC laptop. I was pretty happy, and on familiar ground, until last week's editors meeting at O'Reilly. Since then, I've run screaming back to my TiBook, and am (for now) thrilled...
Is JNI the last answer for native bridges? Is there a better way? Does anyone care?
Need to access HTTP-based resources from your Java application? Check out Jakarta Commons HttpClient.
I'm surprised by Bill Venner's recent discussions on Exceptions with James Gosling and Anders Hejlsberg. Exceptions are one of the best features of Java. I think the problems that Dr. Hejlsberg describes are easy to contain if the development team decides how they're going to handle trouble before they get too deep into their work. Here's what I usually do.
Joshua follows up on a request and shows
how to handle right clicks on anything.
OK, I'm being facetious again. But what happened to all those people warning us about Java optimization?
What's the overhead of casting objects in Java?
Joshua creates a useless busy cursor using the caps, num, and scroll lock keylights.
Joshua uses an event listener to implement simple window snapping on swing Windows.
Today I complain about why Java has no support for transparent/non-rectangular windows.
The second volume of Douglas Dunn's "Mastering The Fundamentals of the Java Programming Language" is available ... for free!
I've just reviewed this book for JavaRanch and I only wish I had found it sooner!
Why, oh why, does Sun not break apart the enormous rt.jar?
Now that building native-looking Swing applications for Mac OS X is easy, will this start the return of the Java desktop client en-masse?
Usability comes from understanding a problem domain and the user's needs - no API can give that to you.
Anecodotal evidence and a licensing announcement appear to indicate a sea change in 3D graphics as it applies to Java.
OK, that's a bit of a contentious (and pretentious?) title. But I claim that toying too much with Java's identity will give C# a big lead.
When organizers asked me what language my hack was in, they were surprised when I said "Java". But that's changing...
It's not just JavaSound that's fallen between the cracks. javax.comm is in a similar state.
I used to think it was a team... turns out its just one guy.