Echo JS 0.11.0

Good question! Yaml could absolutely work, but I found it too verbose. The advantage of a custom syntax is that the declaration is very similar to a .env file (or output from `env`). With yaml it would have to look something like:

```
VAR:
  type: String
  default: VOO
  # no obvious place for comments
```

To me, at least, a terse and intuitive syntax is more important than <insert reason for using yaml here>. However the internal representation looks exactly like that, so in theory it would be possible to support yaml/json too.

I read "I work for nodejitsu – who doesn't like that isaac keeps npm to himself – so we try to overthrow him by using a confusing package name to compete with the very registry it's hosted on. And when exposed I try to frame us as the underdog and him as the bad oppressor".

Yes, that method was mentioned everywhere when i researched available options but I find that it offers unnecessarily low entropy. Oftentimes I need passwords that will only be copy-pasted and so there's no need to restrict one self to typeable passwords.

Also it was a good exercise to build a cli in node.

Note that while x may be private, it's shared for all instances. Might be useful for private constants, but not for variables.