>Just out of curiousity, why would using Java cause you to create flaky stuff.
>
>As far as I know, Java is probably the most in demand language there is right now. I know for a fact that if you have Java and Oracle experience, you can count the amount of time you will be unemployed in hours, maybe a couple days.
>
>I'm just curious as too what problems you found

PMFJI - that's the rough opinion I have of Java currently too. But it may be a fine language/tool in the right developer hands. The problem seems to getting the right hands and/or the right tasks to use it on.

We have one Intranet app done in Java by contractors, it's a fairly simple 8-page or so app that does mainly optiongroup/dropdown/listbox interface for querying a Sybase backend. The queries themselves are okay, but it's just an atrocious front-end. Extremely slow (as in read your newspaper between *every* mouse click), and very buggy. If you do more than a few simple tasks, the web pages distort and then disappear and you have to restart IE and login again. New contractors have failed to improve it much...

No one will attempt a Java app here for a long while after that bad apple - as I say, it may be no reflection on Java itself, but rather the type of interface and/or the quality of the developers that are accessible by the gov't pay standards.

So, what would you think is the cause of such problems in a Java-built app?