I've been doing monster searches over the past few months for a Swing developer here in NYC. I am seeing a lot more Java developers now than I was a month or two ago. Is it because the economy is improving or because it's right after JavaOne.
Basically, this guy set out to write a really small (or smallest) Turing complete language back when the Amiga was king. Apparently, he got it down to under 200k.
Here is the full list of commands.
Sun showed a demo application to demostrate real time Java. There was a thick client application controlling a reverse pendulum (basically a machine that held a stick straight up, like when you balance a ruler on your hand). They had an application along with it to control the motors and display settings -- including failover.
You guys know by now my stance on native look and feel support. I saw some demos showing native looking apps on Mac, Windows and Linux. Very impressed. I know I talk alot about the need to look native. That's definitely my problem space, but I also definitely realize the need to have an application that looks absolutely identical between different platforms.
"JDIC will enable applications written for the Java platform
(Java applications) to integrate more seamlessly with their native
I wish it did. I really wish it did... but it doesn't.
So far, of the people Ive brought in, no one has been able to answer a simple Swing threading question. Several even suggested to use SwingUtilities.invokeLater() for expensive work - not knowing its actually executing in the Swing thread. Im making a point of this because it highlights a disconnect between the design of the Swing API and its users.
Recently, three coworkers compare notes about their work history. Mike
adjusts the pictures of this three teenage children and smiles, "I have
only had three jobs in my career."
Mary laughs and says, "Me too. I've also only had three jobs... but
I've only been working for three years."
Hey all. Been a long time I rapped at ya, so here it goes.
There has been some great talk about usability over the last week. Most of us here are primarily developers or technical managers. I want to remind everybody that there is a whole field of study around usability with several books, websites, conferences, and workshops to help you design your applications.
I took another look at SwingSightings recently, and something struck me -- most of the user interfaces (UIs) for the Swing applications are not very good. I'm not naming names and I'm not saying everything is bad (there are in fact some pretty cool apps up there). What I am saying is that on a whole they are not so great.