I came across a disturbing factoid this morning: "U.S.
The current approach for scaling J2EE applications is to
cluster application servers. Some really good work has been done
and clustering has improved to the point where it's a basic
commodity. Even “free” products such as JBoss and JOnAS
offer complete solutions that include clustered caches to keep
servers in sync.
Every coin has two sides...
My wife and I are not the most practical people in the world.
I was in a meeting the other day where one of my colleagues joked about a manager at our company who insists on calling our staff "Programmers" rather then "Software Engineers". I responded that I had once been an "Engineer", but now I was just a "Conductor". A friend chimed in that she's just a "Brakeman".
All the recent ramblings about Groovy and Jython makes me wonder:
What makes scripting so powerful?
Let's start with what a "script" is:
In a play a script tells the actors what to do.
I came across
Robocode a few years ago and was instantly delighted. On first glance, Robocode is an arcade game. Robot tanks roam a virtual battlefield in search of combat and blasting away at any opponent that they encounter.
Dick Wall's articles on "Integrating Sun Java Studio Creator Into Your Development Process" have got me thinking again on reasons why a lot of software turns out bad.
Perhaps we've made it too easy to write software.
The techno-clairvoyants have been strangely quiet of late... so I am left on my own to predict what "The Next Big Thing" is going to be.
I had intended to write a running blog at the TSSJS, but that didn't happen.