From: Benoit Cerrina <benoit.cerrina@...>
Date: 2002-02-19T16:58:18+09:00
Subject: Re: Ruby and .NET

>
> Um...for as many apps that are written to use COM and OLE, there a many,
> many more that do not.  What about apache, jboss, weblogic, websphere and
> the n-thousands of other applications that do not use COM/OLE?
well I never said everything is COM but I do think that COM/OLE has had
actually
more influence on the way programs are done htat was originally intended and
even
outside of the windows frontier. That was the whole point.  If .NET is ever
used
as extensively as OLE/COM well then it will have done better than I'd hope.
>
> BTW:  I think that COM and OLE did dramatically effect code on Win32...my
> point is everyone who uses COM and OLE are not going to throw that code
away
> to replace it with C#-based stuff for exactly the reason that they are
> "millions of lines of code" :)
>
> Rich
>
definitely agree with that, I think MS is way too smart to do this.  On the
other
hand it is very easy to interface COM and .NET and I'd expect more and more
new
code done for office and other MS projects to be done using .NET.  After all
it is
very easy to use both managed and unmanaged code together which is a great
force of the
..NET framework.
By the way the preceding remark about ruby being able to interface with .NET
in the
same way as with ole through WIN32OLE, I really hope it will do a lot better
than that.
WIN32OLE has a great quality, it exists.  This is about the only thing which
can be said
for it.  Hopefully the integration will be of the same level as perlNET from
activestate
(http://aspn.activestate.com/ASPN/Downloads/PerlNET/More)  that is ruby
still use its C
interpreter, but it is possible to use ruby object from .NET and vice versa.
There is a lot more to COM and OLE than using automation interfaces which is
all WIN32OLE
allows.  What I'd like is to be able to use any COM interface and to be able
to implement
and publish any COM interface as inprocess or outprocess component.
Hopefully this will be easier to do and there will be more motivation for
..NET than for
COM/OLE.
Benoit