curly

Now the language is dead and users are better off migrating to Babel and just dealing with the curly braces and commas.

JavaScript's syntax is less like Java's than any other popular language that idiomatically uses curly-braces to delimit blocks.

For example, it considers omitting a curly brace on a single line conditional to be an error.

But, if you seriously don't use open source code because of where the curly braces are, you're being pretty stupid.

ASI is why, in JavaScript, you always put the curly brace on the same line.

Not to mention placement of parentheses (C vs s-expression), curly braces or angle bracket.

I've been curious how much position of curly braces in C derived languages affects open source popularity.

I'm pretty sure people get more worked up about spaces vs tabs (at least they used to) or curly braces.

In that case I'm almost certain you would go for block only as it is the default in nearly all curly braced languages.

Example: Let's say that I am prejudiced toward piglets (those damn curly tails!).

When I wear a bowtie, for instance, I find I use more curly-braces!

I think using curly braces would be an automatic semicolon insertion hazard.

I can just think in XML easier than remembering "Okay, so there's a bracket here, and a curly brace here, or is it curly brace and bracket?

That said, the formatting in InDesign was kind of a pain on its own (it kept adding "typographers" curly apostrophes which would break the code), but I'd probably still choose that over LaTeX.

I appreciated this little bit of editorializing: "The -> and doto macros save us from having to name each intermediate step and from the unreadable nesting you’d get if you tried to do the same thing in a typical curly-brace language.

I don't think, for example, "semicolons terminate statements; blocks in curly braces; module import is use module::submodule::symbol; comment with // or /* */ which can nest." is deep water.