> The only people who seem to disagree focus on the aesthetics of code over the clarity of explicitly telling the reader your intentions to terminate a statemen

> The only people who seem to disagree focus on the aesthetics of code over the clarity of explicitly telling the reader your intentions to terminate a statement. Okay, I'll bite. I don't think "aesthetics" and "clarity" are disconnected. Clear code looks nice, and nice looking code is clear. I still adhere to a "no-semicolons-needed" approach. The edge cases are few, and I can't recall the last time I ran in to trouble because there was no semi-colon. People not including that trailing comma out of IE-era habits is something that bites me far more often (although you do get an error, but Firefox at least will also issue an "unreachable code" error in your example).