Frans,

> > 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?
> 
>         No, though this situation would IMHO be rare.

I suspect it would be the most common actually.

> > 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.
> 
>         No, I don't expect them to retrain to Java, though 
> it's a solid choice for _THIS_ situation IF you want to / 
> need to support a few hundred linux installs.

My point [almost] exactly. Java is only *one* of many [solid] choices.

> The reason is 
> simply that if you NEED a functionality for your application 
> which relies on something in .NET that's not in mono (and 
> please, don't come to me that that set of features is very 
> small) then you're in trouble.

Erm,...that set of features is very small.  ;-)

More to the point, if that were the case, Mono won't be in the running.

[Unless the cost/risk of implementing said feature is acceptable. SourceGear
sponsored development of some Mono features to ensure Vault clients didn't
have to be Windows boxes for instance.]

> > >         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?
> 
>         What kind of stupid answer is that? Every toddler can 
> answer a 'why' question with 'Why not?'.

I have a cool .NET app. Assuming it can run on Linux using Mono, your
question has no substantive meaning (in the context of this discussion).
I'll run it wherever it pleases me to.

> Please address the 
> question. Choosing the OS the app has to run on is KEY for 
> your project. It's not something you can swap out and replace 
> with something else. Not even with java in some situations. 
> So the question if Linux is an option isn't something simple. 
> Picking Linux has serious consequences for your application 
> and the development of that application. So if you think you 
> can defend your choice for Linux to your boss with "Why 
> not?", I hope for you your project doesn't do anything fancy.

It it can run on Mono/Linux, there is nothing to defend.

If it can't run on Mono/Linux because a needed feature is yet supported, we
have a decision to make on cost/risk etc between:
- adding feature to Mono/Linux 
- extending Mono/Linux version of app to use native Linux substitue of
feature
- rewriting for another toolset/platform e.g. Java, Python, Ruby, C/C++ etc

I sense an undercurrent of Windows vs Linux in your answer. That could be a
valid concern but, it is no longer about .NET, Mono or indeed Java.

> > > 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... ;-)
> 
>         and this is capable of running a full distributed transaction?

Yes. Well, no. Grasshopper is the developer edition. The Enterprise edition
does. So, yes.

> > 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).
> 
>         If it's stalled, how can it still be up to par?

Flippant answer: Well, the Apache excalibur project has been discontinued
but curiously, the code continues to work fine. ;-)

On-topic answer: I wasn't commenting on whether or not Mono's
System.EnterpriseServices support was "up to par". Just addressing Seref's
comments about issues that may prevent or hamper any attempt by the Mono
project to support System.EnterpriseServices.


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

Reply via email to