Re: The Revenge of the Geeks
BGB wrote:
I may be missing something here...
because... it involves linking against and using libraries, correct?...
Not in the case of Java EE explicitly. You use libraries to write your Java code, sure,
just like in Java SE, but there's no link step.
But once you've written a Java EE app, you don't do anything resembling linking. You
upload the app to the application server, which deploys it for you.
like "both languages have libraries, but maybe not the same libraries".
You overemphasize the similarities and ignore the differences.
as in, for Java, you can copy around and use a JAR.
You can, but that's only the tip of the iceberg.
or in C or C++, you link against the DLL or SO, or use a static-library
(which then becomes a permanent part of the binary), ...
Whatever. This does not shed light on the use or value (or problems) of Java EE.
like, for Java there is LWOGL, and for C there is "opengl32.dll".
Nothing to do with this discussion.
or, one person uses AWT or Swing, and another uses GDI+ or WinForms.
Things are always cognate, but that doesn't make them the same.
All analogies share the characteristic that they break down if carried too far.
if you have some program and need to run it on a web-server, it can be
copied over into its "cgi-bin/" directory or similar, or set it to run
at start-up as a deamon (or a as a service on Windows, or launch it via
"start-up applications" or similar).
That's very different from how you administer a Java EE server.
Really, it's annoying that you don't research this first. Bye.
--
Lew