Congratulations to Dino, Harry, and the rest of the IronPython team! They just released IronPython 2.0 which has parity with CPython 2.5. This release of IronPython includes release 0.9 of the Dynamic Language Runtime (DLR).
Download it from CodePlex.
Last week Expansys shipped me a shiny new Nokia E71. This is a follow on to the popular E61/E62, and a significant step up from my E60 which also lacked 3G support on AT&T’s network.
I was thinking about getting an iPhone, but the poor battery life and lack of real keys were a problem for me. It turns out Joel Spolsky got an E71 too – maybe great minds think alike?
The Good
The Bad
So that’s it for my E71 review. I’ll update this post as I get more experience with the device.
Almost everyone I know complains about the performance of their computer when an anti-virus (A/V) product has installed, and thinks they need more memory or a faster processor. Wrong! You need to get a faster hard disk, or disable scanning of certain files.
You’ll see from Task Manager that memory and other resources are plentiful on a modern computer, but page faults and other disk I/O (hidden by default) are occurring at very high levels. Disk I/O is still slow on modern computers and you’ll get better performance gains from improving this aspect.
Most A/V software has settings that let you control:
Making changes to these settings will benefit performance, and security can still be maintained to a very high level. You are running Windows under a normal user account, aren’t you?
Whilst SharePoint is one of Microsoft’s fastest growing products, it’s also one of the most frustrating to develop for. Recently I’ve been been doing some WSS and MOSS site customisations with SharePoint Designer and custom Web Controls. To me this is the type of development that most people will be doing. Most ISVs are doing back end work, further from the realm of the consultant or business developer. Microsoft seems to cater more to the latter group.
Some of my gripes include:
I’m pretty sure these issues are easy to fix, but Microsoft and other SharePoint developers recommend that development is done with the ISV-oriented tools. This is very inconvenient since the product is sold as a rapid development platform and packaging/deployment requires quite a bit of extra effort to get right. Hopefully the SharePoint experience will improve for front end developers in the next release.
IronPython was one of the factors that impacted my decision to attend PyCon. Microsoft are approaching the release of version 2.0 which will have parity with CPython 2.5. The production versions already are close to full Python 2.4 support making it a viable platform for use in a lot of places where I would typically use C#.
Going into the conference I was looking forward to the Sunday session with Jim Hugunin but there turned out to be some more treats for the IronPython developer. Feihong Hsu ran a session on Python.NET and how you can bridge from CPython to the .NET platform, taking advantage of rich Windows APIs. Michael Foord spoke on Silverlight as well as his company’s spreadsheet which embeds IronPython.
Feihong organised an open space session for Saturday evening after the PyWin32 gathering to talk about Python.NET and we were joined by the IronPython developers and management (Dino Viehland, Harry Pierson, Jim Hugunin and others). We discussed a number of aspects of IronPython and progress towards the 2.0 release. It looks like this may be complete in October given that they released the first beta last week. Again Michael Foord had something interesting to say on what Resolver Systems are doing.
Michael presented an open source project called IronClad. This is quite an insane assortment of code from C# to Python to assembler all in the name of accessing Python modules written in C. To date they have the bzip2 module running but are working on support for modules like NumPy which are important to their customers.
After the open space session we headed into Chicago for dinner at India House. This gave us a chance to find out some more stuff about the IronPython implementation, and other factoids. Dino hinted that he was working on getting Django up and running. Little did we know he was going to be demoing this to the crowd on Sunday.
Sunday saw Jim’s big talk and I managed to get a few photos. It wasn’t easy, but I think these turned out a bit better than earlier shots at the conference. Dino showed off the fairly minimal changes needed to get Django running on IronPython and Jim demoed the IronPython interpreter running under Dynamic Silverlight.
After the keynote, Dino gave a me a quick run through of the IronPython and DLR source code. This was very interesting and it gave me a real step up in understanding what goes on under the covers. Thanks Dino!
Brian Lyttle runs Source Foundry, a consultancy
that specialises in Web development and content management. When he's not writing code and experimenting with
the latest tools, you can find him honing his photography skills or helping Bill
to improve his Mazda Miata.
I update my link blog regularly. It's powered by del.icio.us so you can subscribe to the RSS feed.
This Weblog is an experiment, and will focus on a broad range topics ranging from marketing to software, and anything else that comes to mind. These are my views and do not represent the views of any employer or client.