Nowadays a new data interchange format is born more or less every day. Today I saw a couple of posts on MXNA announcing SWX, so, curious as I am I checked it out. Now I shake my head in wonder of how people find the time to reinvent the wheel time and time again.
The reasons for why SWX is not worth a second look are outlined in SWX: a bad idea by Patrick Mineault (there is also a rebuttal to that post on the SWX site).
I do agree with Patrick that SWX looks like a hack, partly because of the questionable implementation of the client side deserializer (which may or may not be just a temporary version) but also because the sample code on the site is so backwards.
loadMovie is used to send data,
onEnterFrame is used to poll for the new data and display it when loaded and then there is the mysterious first line:
org.swxformat.PHP.init(), which doesn’t make any sense in the context. Fair enough, it’s an example, but hello? events? semantic naming of methods? I wouldn’t hire people who wrote code that looked like that, and I sure wouldn’t use their frameworks.
There are so many alternatives to SWX that it’s not even funny. Data interchange isn’t very hard, and SWX doesn’t seem to me like it makes it easier. If you want PHP integration write a WDDX de/serializer in ActionScript, it could be done in 30 minutes tops, or use one of the many JSON de/serializer for both ActionScript and PHP, that makes you less bound to the PHP platform.
SWX doesn’t look simple to me, it looks like a mess. It looks sloppy and backwards.