Originally posted by bolidecaster It is said in the manual that the most serious drawback of choosing .NET is that non-Microsoft platforms are not supported. How do you think of MONO(http://www.go-mono.com/) and DotGNU (http://www.dotgnu.org/)? Thanks!
Originally posted by michi Not wanting to be too biased about it, but I'm skeptical too. Remember the DCOM UNIX implementation by Software AG? That was an unmitigated disaster: it never worked properly and went nowhere.
Originally posted by michi
I also think it is highly likely that MS would fight any moves to make .NET availabe as Open Source.
Originally posted by michi
My feeling is that, if you need cross-platform functionality, you had better not look to MS technology to get it.
Originally posted by marc I really don't want to start a big discussion here, but the original question was about .NET. And .NET != Web Services. .NET is one possible platform for Web services, as are many many others.
Originally posted by rdilipk So lets assume that MS doesn't make .NET Open Source -- so what? That doesn't make the .NET framework any less technologically competent.
Well you are famous for your views on this but I hate to break it to you again that Webservices are the current fad that will lead to cross platform interoperability.[Whether we would end up with CORBA all over again is another matter altogether.
Currently the movement is there and all the big boys (MS, IBM, BEA, IONA...) are putting their money behind it. So its a little presumptous to suggest that its nothing more than collective stupidity.
The original question had nothing to do with web services in the first place. I brought it up only because Michi said that you shouldn't look twds MS for cross platform interoperability. That was true a couple of years ago. If you buy into the web services mantra then this argument no longer holds but if you don't the discussion is moot anyway. We are simply arguing whether cross platform interoperability exists in the MS world -- not whether web services are technically superior or not.
I have followed Michi's posts everywhere and I have learnt so much simply by reading what he writes (and this being I have nothing to dowith CORBA) -- I respect him a LOT. 2 years ago he argued about the importance of source code portability with another famous personality in comp.object.corba. Today he has made a 180deg turn and posted that The much-lauded source code compatibility in practice does not exist.
I am not challenging him (I must be an idiot to do that :-))
All I am saying is people change, views change and technologies gain or lose traction depending on your experience with it.
Originally posted by ganzuoni Hello,
just few considerations.
About portability: no mention to Java.
I think that CORBA C++ portability troubles experienced by Michi,
almost vanishes with Java.
Are you going to dismiss Java support in favour to C# ?
(Don't worry, I think I know the answer !).
And two words on Webservices.
I think that the only advantage is SOAP over HTTP, that lets you
All the rest is a deja-vu with a LOT of missing pieces.
wsdl ("and the idl that it is not", recalling a wonderful article). I challenge
anyone to repeat twice the experience of writing a wsdl by hand.
(I hope Michi not shooting me !).
Well, I think, wrt the situation at that time, POA is a great idea !
Yes, TOO MUCH complicated in many aspects but the separation
of object references from servant, POA current, ServantLocator,
lifespan policy, id assignment, I think that are concepts that
mark a milestone of what a server deployment environment MUST
provide to the applications.