From: arne@vajhoej.dk   
      
   On 10/14/2025 12:07 PM, John Dallman wrote:   
   > In article <10ckadi$7dr$1@reader2.panix.com>,   
   > cross@spitfire.i.gajendra.net (Dan Cross) wrote:   
   >> I thought Microsoft really ran circles around them with Java on   
   >> the client side, and on the server side, it made less sense.  A   
   >> bytecode language makes some sense in a fractured and extremely   
   >> heterogenous client environment; less so in more controlled   
   >> server environments.  I'll grant that the _language_ was better   
   >> than many of the alternatives, but the JRE felt like more of an   
   >> impediment for where Java ultimately landed.   
   >   
   > The main uses for sever-side Java, as I understand it, are:   
   >   
   > It happened to have the right idioms for writing server front-ends that   
   > could distribute requests to the backend efficiently.   
      
   Servlet/JSP looking up remote EJB in JNDI??   
      
   >                                                       Being able to do   
   > this the same way, within the parts of the JRE that are effectively an OS,   
   > on all the different host platforms, was more efficient in developer time   
   > than writing a bunch of different implementations. Developer time is   
   > really expensive.   
      
   I believe the success of J2EE/Java EE/Jakarta EE relates to:   
   1) Money. There was thrown a lot of resources into it from   
       Sun, IBM, BEA, Oracle, SAP, Borland etc.. They simply added more   
       functionality than any other platform.   
   2) Because it was a multi vendor thing, then the model became   
       vendor independent API's - not just in theory but in practice   
       as well. It is actually possible to switch vendor.   
   3) A well working cooperation between the commercial vendors and   
       the open source community.   
      
   Arne   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)