Loosen up the death grip on #19 with `switch`

* `switch` is designed to handle multiple logic cases since ES3 and forward.
* There is no requirement for the prior restrictions in any of the styleguides currently mentioned
* Noted that curly braces can be used for code folding, otherwise they are mostly useless imho and as far as I know
* Added `expressionNth` to the sample with a simple fall through.
* GMs requirement of adding a comment for fallthroughs seems rather tautological since this is how the statement has been in the C family of languages and all of its derivatives for many decades.
Go with GM styled comment requirement of `// fallthrough` syntax instead of curly braces.

* Apply some more of the styleguide to the STYLEGUIDE.md
* Clarify in notation that sometimes a `switch` may not always be the best option for readabilty in some cases.
* Leaving the choice of curly braces up to each contributor for the time being. Code folding is nice but ususally `switch` isn't that complex enough to need that.

Applies to #245 and #19
More symmetry with the styleguide of indent with 2 spaces in the STYLEGUIDE.md examples

* Applies to #19 and pushed in #245
Missed symmetry on 2 indention spaced example.

* Applies to #19 and pushed in #245
Add recommendation for `setTimeout` from #208

* Almost verbatim copied from sizzle

Applies to #245 and #19 and recomendend at https://github.com/OpenUserJs/OpenUserJS.org/issues/208#issuecomment-47728667
Clarify server side usage of node.js specific API

Applies to #208 and implemented in #245
Merge pull request #245 from Martii/Issue-19StyleGuide

Loosen up the death grip on #19 with `switch`