[Mono-list] Please comment on excellent Java/J2EE/EJB v. Mono/.NET article here...

[Chris Seberino]

Jason

Thanks for detailed reply.  Please see my verbage below...

> So anyhow, where I feel he's wrong is:
> 1.) Passport is the real problem, and pressure needs to be applied so that
> this doesn't turn into fiasco so big people will wish for the days with
> InterNIC bungled and abused their DNS rights.

M$ will use PInvoke to tie apps to MS.NET in the name of
increased performance.  They will figure out a way to
tie apps to Passport too.  (Think IE only web sites.)

I think author's point was 
Passport won't be unavoidable so give up now.

> 2.) Java is not appropriate for all tasks. Neither is .net for that matter.
> But what we do need is a loosely coupled platform where different language
> technology's are allowed to interact as much as possible. .net doesn't
> wholely solve that problem, but it definately steps in the right way. We
> should not throw that baby out with the Passport bathwater.

I'm not an expert but I believe there *already* exists compilers
that compile lots of languages to the Java Virtual Machine.
J2EE/EJB won't tie people to Java anymore than .NET/Mono for
this reason.  I believe author wants us to win the war over
the web services infrastructure first. 
After that battle is won we can work on secondary battle of 
adding JVM compilers for all languages and making Open Source
clones of JVM, Java libraries and other Java-isms.

Chris