Coupling in software architecture seems to form a spectrum, based on what has to change to make the system do something different. At one end of the spectrum are dissociated ubiquitous services, like those envisioned by JXTA. At the other end are the highly-coupled systems of architectural nightmares. I haven't found anything that lays out the spectrum well, so here's my attempt.
Passion... motivation... enthusiasm. What does it take to get excited about what you're doing, and once you're excited, what does it take to STAY that way? Try to remember how you felt when you ran your first servlet. Your first distributed (RMI) app... with dynamic code downloading. Your first enterprise Javabean. (OK, strike that last one.)
Lego is supposedly going to kill off its Mindstorms product line.
Are women systematically invisible in the technology industry?
Apple's Steve Jobs flashes the crowd of the MacWorld 2004 conference!
Apple announced the iPod mini today...but with MP3 playing cell phones coming on strong, is it too little too late?
When we're no longer writing programs, do we still need programming languages?
In the old client-server days, we used only two layers: data (based on SQL) and the user interface, which was proprietary. Is that approach now dead? Or are there times when this old fashioned approach to application development is applicable?
Joshua discusses why the networked applications are coming and what UI technology we will need to build them.
Java is notably the first programming language to provide full support for checked exceptions - you must explicitly declare them if you they are going to be thrown, you are forced to either handle or declare to throw them and more. However, after using them for a while, you start noticing that sometimes things don't work so well. I do like checked exceptions, but read this blog entry for some of my thoughts about how exceptions could be different (and sometimes, better)...
How do you query your objects in memory? How can you get subsets of them, averages of amounts and find out about which objects have been created after a specific date? That's all possible with Jakarta Commons JXPath.
The alpha release of the J2SE v1.5.0 SDK is now available directly from Sun but remember to get the latest version of the JSR-166 Concurrency library code.
For 2004, RMH is planning to write a paper and possibly a book on the J2SE, working on the JCP EC, JSR 220, and Geronimo, and consulting.
Do you know there are very easy to use classes in the JSDK for compressing streams? Have you used them? Do you know you can compress your streams even more just by calling one method of a property we ignore? Yes, all of that is true and you can get the details here.
Suppose you have a J2SDK distribution that comes without documentation. How can you use it if you don't know which classes, methods and properties are there? Simple answer: build javadoc from its source code using Ant. Read this blog for a sample build file.
AH! A new year! And time for new resolutions like regular blog entries, playing as many games as possible, and a little pet peeve....
Games aren't just about polygons and collision detection - media is becoming increasingly important.
Data Abstractions are wonderful things, but some times you really need to know the implementation details
I list details about the December Java Performance Newsletter, discuss the responses to last month's question, and give you some site stats.
Do you work with J2EE? How many times have you written code that called setRollbackOnly()? Never called it? I am afraid that is why some of your transactions aren't working properly...