For those of you who haven't heard the latest replacement Podcast by Jim - do so - it's big industry news hidden in the guise of a dog-ate-my-homework message.

Welcome to VisualWorks, start a new project:

• Start a Graphical User Interface Application
• Start a Web Application (Seaside)
• Start a Console Application
• Start a Shared Library Application (DLL, SO, etc)
• Start a Smalltalk Library Component (PCL)
• Start a C Interface Component
• Start a .NET Interface Component

For me, VisualWorks should be an enabling platform. If it enables you to write code and have it run on two or more platforms without change - fantastic. But if that's not possible, then I still want to be able to write the code. Previously, VisualWorks would not invest in libraries or frameworks that couldn't be supported on all their platforms. I'm very glad to see that old style of thinking go.