''.join([chr(x) for x in [112, 121, 100, 97, 110, 110, 121, 64, 103, 109, 97, 105, 108, 46, 99, 111, 109]])
Showing posts with label ironpython. Show all posts
Showing posts with label ironpython. Show all posts
Friday, July 9, 2010
I want to talk to Jython and Iron Python developers
I want to ask some questions of the Jython and Iron Python communities. I'm primarily looking for efforts that can go into publishable case studies. Experience in use of Django in the Jython and Iron Python environments is also very much desired. Please use my email address which is obfuscated below and can be decoded by simply running the code in a python shell:
Tuesday, March 31, 2009
Changing over to .NET
After a lot of thought and meditation I have decided that it is time for a change. This change has been in the works for a long time. I want to belong to something monolithic and proprietary, and I think that .NET on Windows is the way to go.
The .NET platform empowers me with the ability to choose from a host of languages like C#, asp.NET, vb.NET, Boo, IronPython, IronRuby, and many more. And after long and careful consideration I have decided that my next language of choice will be C#.
C# is under the stalwart auspices of Microsoft itself, instead of some guy from Denmark. It has static typing and thanks to compilation most bugs are caught quickly. The curly braces clearly delineate code blocks, and the semi-colons show me when a statement ends. Partial classes will let me spread my object code across many files, and lambda expressions will let me compress complicated functionality into generic functions. Documentation is done via XML rather than the RestructuredText used across the Python community.
Of course, Visual Studio has a lot of visual elements. I am not sure what that means, but being Visual is obviously superior to the TextMates and EMACS I have used in the past. I can't afford Visual Studio yet, but if I don't buy any groceries for myself, wife, and son, I should be able to pay for my copy in only 2-4 months!
In summary this year looks very exciting.
Update: This was an April Fool's joke.
The .NET platform empowers me with the ability to choose from a host of languages like C#, asp.NET, vb.NET, Boo, IronPython, IronRuby, and many more. And after long and careful consideration I have decided that my next language of choice will be C#.
C# is under the stalwart auspices of Microsoft itself, instead of some guy from Denmark. It has static typing and thanks to compilation most bugs are caught quickly. The curly braces clearly delineate code blocks, and the semi-colons show me when a statement ends. Partial classes will let me spread my object code across many files, and lambda expressions will let me compress complicated functionality into generic functions. Documentation is done via XML rather than the RestructuredText used across the Python community.
Of course, Visual Studio has a lot of visual elements. I am not sure what that means, but being Visual is obviously superior to the TextMates and EMACS I have used in the past. I can't afford Visual Studio yet, but if I don't buy any groceries for myself, wife, and son, I should be able to pay for my copy in only 2-4 months!
In summary this year looks very exciting.
Update: This was an April Fool's joke.
Wednesday, May 9, 2007
The Dark Side begins its seduction...
...but I don't think many will convert.
I'm talking about the Python community embracing the Microsoft Silverlight Dynamic Language Runtime (DLR). This lets us write Iron Python for the browser, in the same way that Action Script is used in Flash, or Java in Applets.
It just seems odd. Plus, Iron Python, for all its virtues, has to do some Microsoftisms in order to work. This means that unlike moving my code wrote using cpython on Windows to Mac OS X to FreeBSD to UNIX to Linux, I have to worry about when I move from cpython to Iron Python. So this means we will have a big code set (Iron Python) in DLR that won't work anywhere else.
Bleah.
Here is to hoping that Silverlight does not take off well.
I'm talking about the Python community embracing the Microsoft Silverlight Dynamic Language Runtime (DLR). This lets us write Iron Python for the browser, in the same way that Action Script is used in Flash, or Java in Applets.
It just seems odd. Plus, Iron Python, for all its virtues, has to do some Microsoftisms in order to work. This means that unlike moving my code wrote using cpython on Windows to Mac OS X to FreeBSD to UNIX to Linux, I have to worry about when I move from cpython to Iron Python. So this means we will have a big code set (Iron Python) in DLR that won't work anywhere else.
Bleah.
Here is to hoping that Silverlight does not take off well.
Subscribe to:
Posts (Atom)
