Talk:IronPython
From Wikipedia, the free encyclopedia
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 expanded 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.
-ronnotel (10/15/05)
[edit] see also setence is bad
See also Boo, a language for .NET and Mono based on Python, but has features borrowed from C# and Ruby such as static typing and anonymous closures.
it may give the impression nthat Ruby has static typing which AFAICT it doesn't --Nkour 13:27, 23 November 2005 (UTC)
- yeah. I agree. I was bold and changed it. - David Björklund (talk) 01:15, 24 November 2005 (UTC)
[edit] Simple Windows Forms application
The Simple Windows Forms application section is a how-to, and doesn't belong in an encyclopia article. 165.189.91.148 21:36, 28 August 2006 (UTC)
