Portability is the main concern here as some of us would like to run ahk scripts in Linux without resorting to perl, php-gtk or any other language. Among the (purely coincidental) advantages, Windows users may be particularly interested in the following:
what are the features (other than smaller file size) that make it better in Windows?
[*:2ar5mxmz]Increased performance with syntax jitted to CIL directly or via CSharpCodeProvider for rigorous optimizations i.e. not interpreted like AutoHotkey
[*:2ar5mxmz]Compiled scripts can't be reverse engineered to their source, only CLR bytecode
[*:2ar5mxmz]Security and reliability which managed code has to offer
[*:2ar5mxmz]Scalability (in future) since .NET makes threading, vector computations, SIMD and other hardware level API a lot easier
[*:2ar5mxmz]Native interoperability with other .NET assemblies and COM - I personally find reflection in .NET easier than Java
[*:2ar5mxmz]Modular code base for custom versions or use from other programming languages
[*:2ar5mxmz]Using the most liberal FOSS license means anyone is allowed to use our code for commercial purposes
[*:2ar5mxmz]Our code is completely original whereas about 40% of AutoHotkey comes from the AutoIt v2 code base
[*:2ar5mxmz]Collaborative effort - submit enough high quality patches in SVN and you can join the team
A main development goal is to have 100% compatibility with AutoHotkey. After a version 1 release we plan to develop extensions.
Is the .NET framework the only change (projected or current)?
You may want to point them to #ahk, if they have time I'll be in touch.
I know someone who has a Mac who would be happy to test any pre-release versions you need to test