> > > Frans Bouma wrote: > > > Mono is nice, but ... I can't understand how people want to > > > develop on/for mono other than 'it's cool'.
> > J. Merrill wrote: > > > > So that the work we do can be deployed on either Linux or Windows? > Frans Bouma wrote: > If that's a requirement, why not use Java? Seriously: > first look at the job, then pick the right tool which fits > the job. It's not as if Java lacks any tooling or > functionality or anything. Perhaps because C#/CLI is the right tool. You are incorrectly assuming that Java is the "right tool" for systems that must be deployed on Windows and Linux (or even Oses other than Windows?). Quick example: A) App already develop in C# running on Windows. Need to extend to Linux. Would you recommend first rewriting in Java? B) New app to be developed for a primarily Windows customer base with a few hundred installations expected on Linux/BSD. Exisiting dev team are C#/C/C++/Windows guys. Would you recommend replacing/retraining just so Java could be used[*]? [*] Remember C/C++ is how Java (and C#/CLI) got to the few Oses it runs on. > Ok, if you have a cool .NET app, it's of course not > an option to use Java, but why then use Linux to run it on? Why not? ------------------------------ > Seref Arikan wrote: > Writing once > and running on multiple platforms is not the hardest thing, > but providing an enterprise infrastructure on those platform > is the hard part. Let's assume that we can compile an app on > windows and run it on linux with mono. That's fine, but it is > not usefull for me unless the application can use an > application server. Scalability is a major concern for me (we > are in the hospital information systems arena), and java > gives me a lot of application servers to provide this. I have > always thought that the major problem with .NET is how it's > enterprise features are bound to native services (Com+). > Without such an infrastructure, how can you compete in the > enterprise app domain in a cross platform scenario? > Does mono have a way of providing .NET enterprise services? Yes. But not in the MS System.EnterpriseServices namespace. You can for instance use MainWin's Grasshopper product. Which actually runs your code in a J2EE server... ;-) > This is the main argument that makes me > unable to defend .NET against java in my company, since > providing an enterprise application with no licence cost at > all is possible in Java,(postgresql, jboss, linux) but it's > not possible in .NET "With no license cost" != "with no costs" > I have checked it out as I have written, and as you can see > at http://www.mono-project.com/EnterpriseServices Mono does > not support the features I have mentioned. "Mono does not support the System.EnterpriseServices namespace" is quite different from "enterprise C# apps cannot run on Mono". > Even if it tried > to do so, I am afraid may issues would arise, containing > licence problems with MS, lack of a formal definition of > Enterprise services (to my knowledge) which means any company > or individual trying to do this would not know the extend of > work, and also would produce an incompatible implementation > with other potential implementors. Enterprise services are difficult..no very hard!..to implement but, Mono could certainly implement most of it excepting the COM+ bits (and were doing so). Uncertainties about MS's move to Indigo stalled the project not any technical or legal difficulties (there are no legal issues btw). For a project like Mono, most of System.EnterpriseServices resolves to: IoC + AoP + wrapped-port-of-J2EE-server-internals + service-filters-and-adapters Kunle ----------------------- The best way to contact me is via the list/forum. My time is very limited. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
