Whoa there buddy, no need to stress. Just don't use it.
The only reason why `cake` exists is because at the time that CoffeeScript was first released, there wasn't a "standard" JavaScript build tool, and we wanted the "coffee-script" project to have as few dependencies as possible. Adding a simple way to expose functions to the command line made it possible for CoffeeScript to build itself, without relying on "make" (Windows), "jake" (very rare), or "rake" (a Ruby dependency).
Regarding your comment below -- it's definitely not going to grow. All it does is expose functions to the command-line. See a litany of "closed wontfix" tickets if you don't believe me ;)
Also -- and perhaps mainly -- releasing "coffee" and "cake" binaries together was too cute to resist.
The only reason why `cake` exists is because at the time that CoffeeScript was first released, there wasn't a "standard" JavaScript build tool, and we wanted the "coffee-script" project to have as few dependencies as possible. Adding a simple way to expose functions to the command line made it possible for CoffeeScript to build itself, without relying on "make" (Windows), "jake" (very rare), or "rake" (a Ruby dependency).
Regarding your comment below -- it's definitely not going to grow. All it does is expose functions to the command-line. See a litany of "closed wontfix" tickets if you don't believe me ;)
Also -- and perhaps mainly -- releasing "coffee" and "cake" binaries together was too cute to resist.