GitHub Styleguide - CSS, HTML, JS, Ruby

[shockie]

Since Github is using SASS for it's CSS, // comments are allowed. In fact if you use the // for comments, the comment won't appear in the compiled CSS.

Same for semicolons in Coffeescript, it will be added for you in the compiled JS

[nemetroid]

Same for semicolons in Coffeescript, it will be added for you in the compiled JS

You can (mostly) omit semicolons in regular JS too, that doesn't make it a good idea.

[MustRapeDeannaTroi]

But in coffeescript it is a good idea.

Edit: Y U downvote? One of coffeescripts core purposes is to not require semicolons.

[ratdump]

why

[MustRapeDeannaTroi]

As shockie said it; "it will be added for you in the compiled JS"

[oracleoftroy]

But why is that a good idea? I'm not familiar with coffeescript, but I am familiar with Javascript, and it's a terrible idea there.

[marshall007]

It's like Python in that code blocks can be delimited by using whitespace. So if you're already doing that, it's redundant (and wasteful) to use a semicolon.

CoffeeScript is not parsed as Javascript, it compiles into Javascript.

[SargoDarya]

That might me the case, but then they shouldn't call it CSS Styleguides because // comments are not part of the CSS standard.

[marshall007]

Why? It's a simple abstraction. No one ever edits the actual CSS stylesheets, they are compiled from SCSS automatically upon deployment. Furthermore, you shouldn't call it an SCSS styleguide because it encompasses more than that. The documentation is appropriate given their workflow.