To beat a dead horse, religious arguments notwithstanding ...
I agree that I find taglibs impossible to understand. I end up
compiling the jsp to a servlet, then using the servlet as a skeleton
that I refine and tune, and I finally dispose of the original jsp simply
because I can't wrap my head around taglibs. To me, Java is simpler and
easier for me to understand than the "black magic" of the taglibs.
However, GUI designers aren't programmers, and they typically find java
as impossible to understand as I find taglibs. If your shop has good
separation of GUI and applications disciplines, taglibs are an
indispensable bridge between the disciplines.
C versus C++ ...
In my comparative performance tests of Java (sun jre 1.4.2 b03) versus
compiled languages, Java had raw performance within 10% of the compiled
language. This was not an exhaustive test, but one that was intended to
hit Java's weakest point relative to a native compiler. Both sets of
code were as identical as the language intents allowed, and were
iterated through several identical optimizations to pinpoint different
bottlenecks.
The 10% performance hit was pinpointed to the stackframe that is built
with every {} pair in Java, which in turn eliminates an entire class of
memory leak errors.
For a 10% performance hit, I can live with Java for application
programming. However, I recognize that there are places where that hit
is critical, and I would use a compiled language (probably not C++, I'd
prefer pascal derivatives or even assembly, but language is a personal
preference, not a functional issue now days).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
