As long as we're talking about word processors that have come a long way since we last talked about them: Mac users should sit up and take note: NeoOffice 2.1 arrives on March 27th.

NeoOffice is a OS X port of OppenOffice.org by a group of developers who have thought from the beginning that the Main OO.o team was taking the wrong tack in offering X-11 support on the Mac. Early NeoOffice releases were all-Java wrappers for OO.o (and were known as NeoOffice/J); recent releases have been Aqua native and, as of version 2.0, included both Intel and PPC binaries. NeoOffice 2.1 will include all the features of OpenOffice.org 2.1, including support for Office 2007 XML documents and Virtual Basic (VBA) macros. And, of course, possibly the coolest icon of any app on any platform.

NeoOffice also includes NeoLight, a plugin that allows Spotlight to index both content and metadata of OpenOffice and OpenDocument files. Users of main openOffice.org distribution can download NeoLight as a stand-alone application.

NeoOffice releases are named for the OpenOffice releases they're based on. Since this isn't an official OpenOffice.org release but a project based on OO.o, NeoOffice releases tend to lag a little behind their official brethren, so NeoOffice 2.1 will correspond to OpenOffice.org 2.1, which has been out for a while. While that sometimes means not being on the cutting edge, the NeoOffice release cycle does have a couple of advantages for uses. The most important, of course, is that NeoOffice is a native app. A less obvious benefit is that by the time a Neooffice release is rolled out, it contains the first several rounds of bugfixes to the OO.o codebase.

For those of you who just can't wait, there is still a NeoOffice 2.0 version available for download, and an Early Release version of NeoOffice 2.1 is available to people willing to support the project with a donation of $25 or more.

The open source Mono Project, which is sponsored in part by Novell, Inc. announced today that it has developed a Visual Basic compiler which allows software written in Microsoft's most widely used application programming language to be compiled and run on any platform which Mono supports. Until this announcement, Visual Basic applications could only be run on the Microsoft Windows family of operating systems.

"The ability to write software that runs easily across multiple platforms has long been a holy grail for developers," says Mono Project founder and VP of developer platforms for Novell, Miguel de Icaza, "The Mono Visual Basic compiler is a milestone step forward in this direction. Using the software skills they already know, developers can now reach a much broader audience, creating applications that run without modification on all the major operating system platforms."

It isn't de Icaza we have to thank for the Linux VB compiler, at least not in full. Google's Summer of Code project in 2006 brought Raulf Jarve, a Norwegian student programmer who now lives in Spain, to the project. Jarve finished the compiler and has since been hired by Novell.

First, let me start with the full disclaimer: I develop Windows .NET application by day (and by night too for ecto) and use Mac OS X at home for everything else. Before getting my Mac Pro last December I used to work on ecto using a second Windows machine, but since then I have been using Visual Studio 2005 in an XP virtual machine using Parallels.

Whether you love or hate Microsoft, you have to give them credit for popularising programming on Windows. While I was a junior programmer fresh out of college learning C++ and working on train control software, truckloads of CS/Engineering graduates were learning to program in Visual Basic. Whatever faults VB has, the way it allows even beginner or causal programmers to learn the craft and produce quick and dirty applications means that programming for Windows was no longer the eminent domain of the traditional CS/Engineering graduates, where FORTRAN and C/C++ rules. Microsoft continues this trend with C#/VB.NET and the .NET Framework, providing a lot of built-in functionality that used to require hand-crafted code or expensive third-party libraries, freeing up developers' time to concentrate on problem solving instead of mechanics.

With OS X, Apple began with Objective-C and Java as the programming languages of choice but ever since version OS X 10.3 Java had been put onto the back burner and is expected to be phased out eventually. Unfortunately, making Objective-C the sole language of the platform also makes it difficult and 'expensive' for Windows programmers, such as yours truly, to join the party. The difference in syntax (despite the 'C' in the name it does not have much resemblance to C or C++), difference in framework and API, difference in IDE philosophy, and the lack of refactoring tools (ReSharper, CodeRush, etc.) and unit testing tools (NUnit, JUnit, etc.) mean that some of the more open-minded programmers (mostly Java and .NET) will not take an active interest in Apple software development.

The upcoming Xcode 3 looks like it would make a big step in closing the gap, but the IDE still lacks the tools mentioned above to attract the time-constrained, less hard core developers from the Windows side of the world. The dark horse may be the combination of Eclipse IDE and Mono project. The Eclipse IDE is mature and has a flexible plug-in architecture so refactoring and unit testing tools can be integrated into the IDE by third party developers. Meanwhile the Mono project has been making lots of progress as far as compatibility with Microsoft's implementation is concerned. And the ability to take code written in Windows and runs it in Linux or OS X (with some limitation, of course) will appeal to Windows developers, at least as a starting point.

In fact, Eclipse/Mono may actually achieve what Sun tried to do with Java all those years ago. Remember 'Write once, run anywhere'?

If you have applications written in Visual Basic 6 (VB6) it would force you to rewrite the entire thing to bring it into Visual Basic.net. Have no fear, an add-in tool from Microsoft is here. Microsoft's Interop Forms Toolkit 1.0 (free download) is an add-in for VB6 that will bring .net WinForms to your VB6 application. Microsoft's goal here was to help developers stuck between both worlds to develop code and focus on business needs in their VB6 apps while slowly moving the application to the new world of Visual Basic.net without rewriting everything from scratch. This allows you to include many newer ideas into your older apps easily, such as RSS, web services, and newer multimedia components.