From: Gregory Ewing on
Tim Roberts wrote:

> I'm not sure that's really fair. The .NET Common Language Runtime is a
> vast and very useful class library, including two complete GUI systems. The
> thought was that IronPython and IronRuby would let people who were
> comfortable in those languages tap into the CLR.

Is there any way for a non-.NET program to access a .NET library?
Or is it necessary to drink the entire bottle of .NET kool-aid?

--
Greg
From: Steven D'Aprano on
On Tue, 10 Aug 2010 18:42:35 +1200, Lawrence D'Oliveiro wrote:

> In message <7fr16650meigqgmj8rh0n3a66q9r4j4eva(a)4ax.com>, Tim Roberts
> wrote:
>
>> The .NET Common Language Runtime is a vast and very useful class
>> library, including two complete GUI systems.
>
> Used only by corporate code-cutter drones.
>
> Go on, name one creative thing which was ever done in Dotnet.

Not just Dotnet, but Python on Dotnet.


http://www.python.org/about/success/resolver/
http://blog.jonudell.net/2007/09/27/first-look-at-resolver-an-ironpython-based-spreadsheet/




--
Steven
From: Steven D'Aprano on
On Tue, 10 Aug 2010 20:07:06 +1200, Gregory Ewing wrote:

> Tim Roberts wrote:
>
>> I'm not sure that's really fair. The .NET Common Language Runtime is a
>> vast and very useful class library, including two complete GUI systems.
>> The thought was that IronPython and IronRuby would let people who were
>> comfortable in those languages tap into the CLR.
>
> Is there any way for a non-.NET program to access a .NET library? Or is
> it necessary to drink the entire bottle of .NET kool-aid?


http://www.mono-project.com/Main_Page



--
Steven
From: Stefan Behnel on
Steven D'Aprano, 10.08.2010 10:04:
> On Tue, 10 Aug 2010 18:42:35 +1200, Lawrence D'Oliveiro wrote:
>> Go on, name one creative thing which was ever done in Dotnet.
>
> Not just Dotnet, but Python on Dotnet.
>
> http://www.python.org/about/success/resolver/

At the very end of that article, I found this statement:

"Resolver One is Windows only"

This sounds like a major drawback to me. It might be an acceptable "early
project priority" if the app is only targeting the desktop, but this system
additionally claims to be a "web-accessible spreadsheet". If this is
supposed to run on a server, it means that it will always suffer from the
"headless click-here-to-continue" problem.

It might not be too hard to port the app to Mono, but the rather explicit
claim above doesn't make me feel very comfortable about that upgrade path...

Stefan

From: Ben Finney on
Steven D'Aprano <steve-REMOVE-THIS(a)cybersource.com.au> writes:

> On Tue, 10 Aug 2010 20:07:06 +1200, Gregory Ewing wrote:
> > Is there any way for a non-.NET program to access a .NET library? Or
> > is it necessary to drink the entire bottle of .NET kool-aid?
>
> http://www.mono-project.com/Main_Page

Anyone thinking of using Mono needs to be aware of the dangers of
software patents in general, and of .NET in paticular.

The copyright license for Mono is under free software terms. But that
gives no license at all for the patents. Novell, who have an exclusive
deal for those patents, happily encourages use of Mono by third parties.

The controversy has raged for a number of years. For more coverage than
you have time for, see <URL:http://techrights.org/wiki/index.php/Mono>.
The issue has polarised discussion, unfortunately, and there is a lot of
name-calling and hyperbole on the record now.

As the Mono site hints, the patent situation for .NET is *very* muddy.
Microsoft hold patents covering much of .NET, but have made a
(non-binding) “Community Promise” that applies to *some* parts of .NET
<URL:http://www.mono-project.com/Licensing#Patents>.

--
\ “It is seldom that liberty of any kind is lost all at once.” |
`\ —David Hume |
_o__) |
Ben Finney