IronPython Moving Forward Again
immytay writes "
Jim Hugunin (Jython, Numeric, and
other projects) has issued the first release of IronPython
since joining Microsoft in August of last year. IronPython
runs on .NET and Mono and is supposedly faster than the C version of Python. This
new version is 0.7,
while 0.6
was released last summer and covered here.
According to the IronPython mailing
list, Jim has help from a Microsoft co-worker, and he plans to work toward IronPython 1.0."
What you will find is that this is a bunch of BS. They took advantage of the new features in the .NET Framework 2.0 - which will be standardized in the CLI. .NET 2.0 isn't even out by Microsoft yet - so of course Mono isn't going to support it.
But Mono is planning on eventually having full support for .NET 2.0. So it will work.
Wait till 1.0 - everything will be working then.
"Ideas without action are worthless."
No, I think we need t.
Every platform that has a .NET implementation already has a native Python implementation, which makes Hugunin's work, while interesting, ultimately redundant. I would love to hear how this little side project reinforces Microsoft's monopoly power in operating systems.
This sig intentionally left blank.
As Edd Dumbil pointed out, there's a number of questions that need to be answered before it is worth getting behind IronPython, such as:
- Is it actually Free Software?
- Why do I need a passport account Passport to participate?
- Why are you bothering to release source code if you're not willing to
accept patches?
- Why don't you want to get it working with Mono?
And so on.
-- "So, what's the deal with Auntie Gerschwitz et all?"
Groovy has been taking a lot of heat lately. Boo seems not to suffer from the management/community problems Groovy has. In fact, Boo is just plain more exciting; Groovy is just Ruby disguised in Java syntax, as far as I can tell, whereas Boo takes what's best about Ruby (heavy emphasis on closures/blocks), Python (indent-based scoping, first class functions), and C# (static typing, properties, annotations, "using", p/invoke, .NET native), and one-ups them with type inference. It really does provide the best of both static and dynamic typing; there is NO compromise here as far as I can tell.
As a bonus, the tool support is already very good. As with any self-respecting scripting language, it includes an interactive interpreter. (Boo scripts can be interpreted or compiled.) The Visual Studio .NET debugger already works with Boo, and if you write your Boo code in SharpDevelop (a free IDE for .NET platform) you can get code completion, syntax highlighting, code folding, etc. And since it's all statically typed, there is hope for IntelliJ-like refactoring tools, although I don't think any exist yet.
Bottom line, I think any Python, Ruby, or Groovy fan should take a long, hard look at Boo. You will find a whole lot to like.