A
Adie
You either encountered poorly designed applications, or your negative
experience stems from the pre-1.5 Java GUI. Sun was making steady progress,
improving Swing performance, and as of Java 1.5 (actually, even 1.4.2) the
GUI response is quite comparable with the native apps.
So we've had the insuferably poor performance for how many years? And it's
*just* improved in 1.5? Comparable to a Delphi, VC++ or heaven help us; a
VB application?
If the server runs Windoze - the weekly (never mind by-weekly) reboot is a
fact of life. Whether the app is written in Java or any other platform is
immaterial. The crap comes from M$ OS.
All 400+ of our servers are Linux boxes.
"Real programmers don't eat quiche". Statements of this kind are a hallmark
of immature wizkids that hold on to this belief until they get into the
'real' world. Then they quickly discover that:
Hey, very much real world here sweetums, we have Java developers falling
outa the cracks in the walls - several hundred of 'em. I get the pleasure
of writing the damn specs and project managing the buggers - used to have
the pleasure of writing the damn code and being managed.
a. lots of 'real' aplications are written in Java (Oracle Management Tools,
for a quick reference)
And it sucks. You cant hold that pile of poop up surely? It's horrible.
Mind you, what's the Oracle server written in? Java, nah.
b. 'real' engineers work with what is most suitable for the task at hand. If
the task calls for a robust, OO, cross-platform, multi-vendor solution, Java
is the way. If the task calls for a distributed, or web-based solution, Java
is the _best_ way.
Cross-platform, multi-vendor screams C++ with a framework of choice, to me.
Distributed, then yes, with app-servers and DB support Java becomes a
potent tool.
Web apps? Anthing .NET kicks Java squarely in the teeth.
Can you tell I dont like Java ;-)