Yes, AppleScript is only one implementation of the OSAScript specification, which is why the shell command to execute OSAScripts is called
osascript instead of
The projects that you mentioned above are exactly what I was referring to when I wrote "However, the HFS(+) filesystem also uses resource forks to store metadata for files, which 'traditional' languages can't access without special methods."
There comes a point where a line has to be drawn that separates what will and won't be covered in a piece of writing; I decided to gloss over those details because I didn't feel they were necessary to the point that I was trying to get across at that stage in the article: that AppleEvents provide a much richer method of passing data back and forth than plain-text streams through standard input/output.
I would like to thank you for pointing out that information in the Comments section, as it provides a way for the readers (and myself!) to find out more information relating to the topics covered in the article.
As for the broken zip file, it was created using Panther's "Create Archive" command from within the Finder. If you expanded the archive with another tool (such as Stuffit Expander or WinZip), then yes, the resource fork may not be attached to the resulting file. To work around this problem, I've posted a copy of the script in SIT format to: