So, what's everyone's opinion on curly brace placement?

oh brother, if you adopt second one and do JS, you are in for a big surprise.

++ for option one
And
-- for option 2?
😋

@4by10 you! I like you! :D

Left option. Second is just...wrong

@KeyWeeUsr i would have liked you back, but all these exceptions are keeping me busy!!!

Option 2!!! I mean seriously how do you see through that mess that is option 1? :D

@Maverick25 good spacing, short if statements and I haven't had a single problem with it. The second is only annoying, because it breaks the style. :(

@KeyWeeUsr yeah I guess it depends on the style :) for me it gives me a better overview where is the start and the end..

@Maverick25 also highly depends on the editor too. If it highlights brackets or no, etc. And your first language is also the important thing e.g. if you learned basic or pascal, this might be the case where second style is used the most and e.g. C/C++ goes with the first.

@KeyWeeUsr very true

Number 2 please. Mostly because that's how VS auto formats things by default.

Option 1 please. :D

And there are those with:
if (condition){ statements....; }

trust me, I've seen some classmates do it.

First every time... Less key strokes and you see exactly what the opening brace belongs to on the same line, and any good editor will syntax highlighting so you know where the brace ends.

I started in C. and most C89 code you see out there has the brace on a new line.

but I typically write it on the same line now a days.

I tried both styles before and I stayed with the second because I can easily see where my opening and closing braces are at and can debug much quicker.
I also sometimes do my set/get or other statements in a single line since they aren't big or that complex to understand/see.

super overrated. mix everything and throw into a blender

the first one is the only way to go, everything must stay clean and in line!

Option 1, if you have a choice. The extra line break annoys me and my scrolling finger.

As I read the opinions, there should be some converter in each sane editor with an option to choose the default style, because man, this can increase your pressure in seconds if you hate the other side...
however, git won't like it (crappy diff).

@benyitzhaki there is a place in hell for people like you ;) haha

@KeyWeeUsr maybe there should be a bit plugin to convert it to a house style on each commit, so each user sees what they want but it's all stored the same?