IronPython, IronRuby, JRuby and the Python and Ruby Communities

By Michael Foord -
My commentary on the Ruby community reaction to IronRuby and comparisons with both JRuby and IronPython:

IronPython, IronRuby, JRuby and the Python and Ruby Communities

Of particular note is that the loss of 'multiple engines' from IronPython 1 to IronPython 2 (the jump to the DLR) may be more significant for IronRuby than it is for IronPython.

Comments

Post a Comment

Popular posts from this blog

In memory: Michael Foord 1974-2025

By -
Image
I never met Michael in person, but we communicated online about all things Python. He was one of the most prolific contributors to this blog during the heyday of IronPython. If you use Python, chances are you've benefited from something Michael contributed to the ecosystem. I will miss you, "Fuzzyman." In memoriam: Michael Foord
Read more

Extending Abobe Flash Player and AIR with Python and Ruby

By Michael Foord -
An intriguing blog entry about an Adobe experimental project. It is a C/C++ cross- compiler for the flash player and AIR. This means that you can (will be able to?) cross-compile the Python / Ruby/ lots of other language runtimes and then run them in Flash. The blog entry contrasts this approach to the DLR which requires the re-implementation of dynamic languages - hence IronPython and IronRuby. The project is already beyond proof-of concept, they even have Quake III cross-compiled and running in Flash. Extending Adobe Flash Player and AIR with C/C++ Cross-Compiler Quake 3 has already been ported to managed code , but this is even more impressive. Whether the Python interpreter can be cross-compiled to run on top of another runtime (with completely different basic types), without changing the language semantics at all, has yet to be proved - but it is a very interesting project. (It also means that Python/Ruby will possibly be enabled only by additional optional downloads - but don...
Read more

Further Adventures of the Debugger

By Michael Foord -
Harry Pierson (Microsoft IronPython PM) has been experimenting with writing an IronPython debugger ( ipydbg ) on top of the .NET MDbg APIs. When we last left him , he had implemented Just My Code (JMC) support allowing you to step into IronPython code. Since then he has made a lot of progress including a colourful REPL (interactive console) and solving some difficult problems around getting to real values behind boxed IronPython variables (needed for showing local variables). He has blogged extensively on what he has been up to (more recent posts last): Showing Source Code Colorful Console IronPython ConsoleColorMgr (the colorful console code pulled out into a separate IronPython module) A Little Hack...err...Cleanup Getting Local Variables Displaying Values Command Routing Getting Arguments REPL Console A lot of functionality is now present. In the command routing entry Harry outlines the seven commands supported by the debugger so far: Continue, Quit, Show Stack Trace, Show Locals, ...
Read more