As an application on the AppDB, we don't have the muscle to encourage bug-fixes off the core team. As such, we either sit and wait on it, keep on submitting out bug reports and voting on the BYOND 4.X app entry, or ... we can submit patches ourselves.

The latter means doing things like implementing ole32 (if you want BYOND out of the box). We essentially have "reverse engineer bits of Windows" (admittedly there is the WINE people to aid with the docs on that), or "reverse engineer BYOND's shared objects", as a technical progression toward BYOND working on Linux.

If the words "reverse engineer" didn't live in the native solution, I would monumentally back that idea. It would be a fantastically quicker route toward a linux BYOND client. However, as it stands it would seem that pesky phrase isn't going away (due to the understandable workload involved in probably even producing API-stubs on the BYOND staff's part), so I guess the technical focus should be on WINE. So, who's up for some WINE programming? =P

Edit: FlameSage, please open up the LinuxGuild to non-members, I've been waiting on posting there for about a year now.

If people will excuse the off-topic, there is an option to allow non-members to post in the forum, seen as I can do it in the RoleplayersGuild. =P Of course, you could always buy me a membership.