You're tan though, so you're only pasty on the inside. :D
Curious as to why #1?
Printable View
I'm #1 as well. I'll go so far as to function() { code;code;code; }, too.
For me, has to do with compressing lines of code so I can see more of the flow in one screen. Even on big monitors with 70+ lines I hate having to scroll up and down to see functional blocks on one screen if I don't have to, and when I'm stuck on 80x25 line terminals or worse it becomes extra important.
My editor tracks indents and brace-matching, so I don't need visual blocking to follow it.
Function #2 is correct
The last thing I want to do is spend time hunting thru complex nested code for a { and its matching matching }
I find it harder to read. I like anything I write or have to read to be in nice blocks and no chance of missing something.
I also indent like crazy so I don't have to guess where something's nested place is. Thankfully, none of this is a present concern. I've only had to really write code for classes and a few for work that were really just to automagical some stuff *I* was doing.
You're not one of those "Your code should be simple enough that you don't have to comment" types are you?
I comment more than the other developers I work with, I put in lots and lots. I've always used K&R code style so it's just what I'm used to. Every place I've worked uses it. In the end it's a matter of what someone is comfortable with. I will say that if you work for me I'll make you use K&R.
https://memeworld.funnyjunk.com/pict...7e_6967534.jpg
https://bigmemes.funnyjunk.com/pictu...74_6968381.jpg
https://memeworld.funnyjunk.com/pict...de_6967672.jpg
Probably because he wears those stupid skinny pants with the elastic at the bottom.
https://bigmemes.funnyjunk.com/pictu...31_6968223.jpg