Hi there,
well, honestly, you're at least in a possition where
you can make a choice.
We here are, on the other hand, solely dependant on IPy.
There are no alternatives to what we're using here at the
studio.
But even still, I think IPy is such a powerful tool that
even if Microsoft ditched its support, we can use and
leverage on it for years to come. At least in our
case.
But I seriously doubt Microsoft will completely abandon IPy
as that's the only Python alternative for .NET.
The .NET CPython initiative is almost dead. I haven't seen
an update for ages, unfortunately.
But if IPy is ditched, I'm afraid I'll have to reorganise
a lot of software here at the studio, that is solely dependant
not on Python, but on .NET. Since without IPy, .NET isn't of
any use for us here. We don't use VB or C# or anything else
similar.
I hope Microsoft will continue to actively develop IronPython,
though.
Lukáš Duběda
Director
[T] +420 602 444 164
duber studio(tm)
[M] i...@duber.cz
[W] http://www.duber.cz
[A] R.A.Dvorského 601, Praha 10
[A] 10900, Czech Republic, Europe
On 18.8.2010 19:41, Max Yaffe wrote:
I've been reading the buzz around Microsoft's reduced commitment to Iron*
languages and wondering if I should rethink my own commitment to IronPython.
To fill you in, I'm a designer of instruments and software for scientific
data acquisition and analysis. My current software uses a dynamic language
for scripting in a Win32 based framework program for acquisition and VBA
scripting in a VB program for analysis. We decided to rewrite the whole
thing in C#+.Net4+IronPython.
On stackoverflow, someone asked about using Iron* vs PowerShell for
scripting in a C# application in light of Microsoft's changing committment.
This was my answer:
I'm in a similar position.
I decided to use IronPython scripting but ever since I saw Anders
Hejlsberg's
talk "The Future of C#", I've had a feeling IronPython was doomed.
It was in Microsoft's interest to get the DLR developed but they
ultimately
want us to use tools and languages they control. After all, aren't you
using
C# and not Java? So what will a Microsoft dynamic language look like? How
about dynamic, interpreted C# (Iron C#)? Hejlsberg's talk made it clear it
isn't that far away. He even had a console window with a REPL interface.
That said, there's always a possibility for Iron VB. Talk about closing
the
loop.
On the plus side for us programmers, Iron C# also solves another problem
that
I'm having trouble with -- the existence of two parallel object
environments,
one of .Net objects, one of Python objects. It takes work to get from one
to
the other. I assume an Iron C# would utilize the .Net class structure.
My advice: Stick with Iron Python and .Net classes. When Iron VB or Iron
C#
happens, it'll be a quick, maybe automatic, language translation. Besides,
if enough of us use IronPython, Microsoft may change their mindset.
So my question to you is a) am I thinking correctly about the future of
IronPython, and 2) if not IronPython, what scripting language should I be
considering for a .Net C# application? I should let you know I'm also
considering switching to Qt/PyQt/Cpython.
Thanks for your input.
Max
_______________________________________________
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com