Added note about cookiecutter

README.md

@@ -82,6 +82,8 @@ Note that this may have security implications. Inspect post-generation scripts c
 
 Sort of. Maven and Gradle both had the notion of "archetypes", which is conceptually similar. There are projects like Mr. Bones for ruby, and even IDE-specific solutions such as Eclipse or Visual Studio's project templates. That's to say nothing of all the framework-specific project generators. But I've grown tired of learning a new template scheme and cli interface for every language or framework, I just wanted to have one set of templates that were all user-defined, easy to share, and all using a unified parameter interface.
 
+[Cookiecutter](https://github.com/audreyr/cookiecutter) is a cool project which meets similar goals, but has many drawbacks. It requires a python installation, needs either STDIN input or an *rc file, has logic-based templating, can't create templates from arbitrary directories or archives, seems to aim for monolithic templates, cannot do parameter joining or recursion, and doesn't seem to support post-generation scripts; making it difficult (if not impossible) to use for languages like Ruby, C-sharp, or Java (which I, at least, spend a lot of time in). `wisk` uses small, direct, purposeful skeletons to create many similar projects, it's not meant to make a monolithic language/framework template which fills every conceivable need that one may have of a project in that language/framework.
+
 ###Branching
 
 I use green masters, and heavily develop with private feature branches. Full releases are pinned and unchangeable, representing the best available version with the best documentation and test coverage. Master branch, however, should always have all tests pass and implementations considered "working", even if it's just a first pass. Master should never panic.