Jump to content

Talk:IronPython

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Ronnotel (talk | contribs) at 02:42, 16 October 2005. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

My understanding is that IronPython is not attempting to be a complete Python implementation. Can someone please further describe what IronPython really is other than just the whole python on dotnet rigamaroll?

I expanding this article by describing (in my view) why IronPython make sense. Essentially, when developing a complex application framework, the server-side developer rarely understands how the downstream client-side developers will want to use the framework. Therefore, it often makes sense to push responsibility for developing analytics from the server-side to the client-side.

IronPython greatly simplifies this objective, particularly since .NET is fairly rigid in the way it supports dynamic code structures. By integrating IronPython into an existing framework, the server-side developer, with minimal work, can greatly expand the range of analytics that client-side developer has access to. Instead of tweaking the interface everytime a new request comes in, the server-side developer can concentrate on maintaining clean data structures.

I highlighted this with a short example.

Hope this makes sense.

Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:IronPython&oldid=25630334"