Java’s Untimely Repainting
One of the biggest problems with Java is that it doesn’t apparently by default repaint quickly enough. If you get it thinking about other things, it forgets to update its interface properly.
Take for example this Java applet I found via Knowing .NET. You go there, enter a URL, and it displays a word analysis of a Web page, like this one for QAHY:
Now, click Open in Window to pop it into a new window. The applet beneath remains. Now, drag that new window over the original applet, and it doesn’t repaint itself while the window is open:
I’ve seen this many times in desktop environments, too. Sadly, Java seems unprimed to repaint smoothly without some attention from its developers. Regardless, in non-Java environments, this unrepainting tends to occur when the application is biting off more than it can chew of the processor or something’s going horribly wrong, and users will pass that particular sentiment over to your Java application that might be otherwise working fine.
And if the users think something’s screwed up, they’ll chew up your support time or not use the product at all, which seems to me less ideal for your organization than just inserting the code to handle this better.
