Trying to bring together a disordered array of thoughts on the subject of evolving Java as a language.
That didn't take too long. Neal Gafter has posted the first closures puzzler.
Last weekend i went and bought a new laptop (actually, this is my first laptop). So, as i plugged it in and connected to the net, Vista started downloading updates and installing them. And then i started thinking - what happens if one of these updates will simply crash the OS on the next boot?
The implicit assumption of any update to the operating system is that it at least boots (if everything...
So, what turns a programmer to a Java programmer, and whom would you prefer on a Java project, an excellent Perl developer or a good Java developer?
If you are working in Eclipse, you will find that Mylar plugin can be very handy. It monitors your interaction with the workspace and filters out the classes / methods / fields that you do not use or change. The resulting view of the workspace is much more focused on your current task.
Every year, a couple of "golden hammers" die and a couple of new "golden hammers" are (re)invented. Bloggers proclaim the new kings, consultants rush in for a quick buck, managers start believing that they will be able to ship the next version on time... Where does it leave us, the guys who actually get stuck with these hammers?
The singleton pattern must rank one of the most-widely used. We all know the pattern and its benefits. Joshua Bloch taught us how to ensure single-instance when the class is Serializable. However, it's quite easy to make any number of fully-functional instances of your singleton class using a simple ClassLoader trick.
With the recent proliferation of IDEs, a Java developer should be aware not to fall prey to the "shortcut lockdown" honeycomb trap.