.gmk encryption

.gmk encryption is the term that refers to the fact that Game Maker 7.0 and 8.0 .gmk files are encrypted. The feature was introduced in Game Maker 7.0, since its second beta, and has caused a lot of controversy amongst the Game Maker Community. It could be one of the most controversial features (or as others simply call it "changes") in Game Maker, since it stops Game Maker-related projects such as g-java.

Background
Mark Overmars, creator of Game Maker, has previously expressed his opposition to projects such as G-Java which converts Game Maker files (.gm6) into compiled Java applets. So, he decided to encrypt the Game Maker source in version 7.0 to limit access to the actual source, even when not compiled!

Arguments for the encryption
Those with the encryption mainly believe that programs like g-Java would do more harm than good to Game Maker itself. Mosts arguments are actually concerns of how such programs would reflect on the image of Game Maker. Such concerns include: So, Mark decided to make them incompatible early on so that no such problems occur on a larger scale.
 * Users would blame Game Maker for errors in conversion, even though it is most probably the converter
 * Users would complain about any major changes in Game Maker that would cause incompatibility with such converters

Arguments against the encryption
Those not supporting the .gmk encryption are largely disappointed by the "lack of sufficient arguments" Mark Overmars has to do do the encryption. There was only one main argument for encryption, was presented by Mark Overmars, however more against the encryption existed:
 * The .gmk encryption would limit projects like G-java, which are good to the community
 * Valuable developer tools such as a resource extractor for corrupt files wouldn't work any more
 * A source code is a source code -- it doesn't need encryption
 * Those working on G-java might decide to work on separate tools that compete with Game Maker instead of extending it.