Phillip, > > Neither does Java. Yet, starting from a .NET app, you > started off by > suggesting Java was automatically a better choice for > reaching other OSes. > > And IHMO, it most assuredly is the clear choice for maximum > cross platform maintainability.
Even more so than Perl?. C/C++?. Ruby?. Tcl?. For high concurrency network servers apps?. Or just web apps?. What about device drivers?. I think you generalize rather loosely. Java has it's limits as does Mono or any other tool. And it owes it's cross-OS capabilities to *other* tools. > Does the phrase 'write once, > run anywhere'(WORA) ring a bell? Yes. So does "Write once, test everywhere." actually. Tiger is cool though. > This phrase is largely > viewed with a tongue in cheek smirk by most of the M$ crowd > I'm sure. However, well defined Java applications that take > various JVM's written for various Oses into account have a > much better shot at running with little or no debug. Take various JVMs written for various OSes into account?. What happened to WORA? Just joking, that's a pragmatic pov. Any analysis of what Mono represents/offers should be equally pragmatic I think. My factoids?. - Java reaches more Oses than Mono currently does. - Java has better cross-platform support for "enterprise" apps. - The overwhelming applications of applications aren't "enterprise" apps. But this wasn't about that or indeed Java. It was about Mono as a cool open source project that offers an option for extending .NET apps to other OS platforms. Kunle =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
