This is my personal preference too. I like that the condition is visually separated from the wrapping. I'm also prone to borderline-too-complex conditions, and this syntax makes those easier to focus on.
With occasionally obtuse syntax: yes; with bonus space parentheticals: no (see?).
Most non-code writing is going to be read linearly, rarely more than onc. Parentheticals in a reading context are secondary, not deserving of additional emphasis that they get in code.
Ugh... This is the type of thing I love about languages like ruby and python, this kind of crap debate doesn't matter, there is really pretty much one way to write it.
Braced languages annoy me because every developer seems to have their own "special" brand of stupid formatting. Some perfect examples of this thinking are right here:
Think about basic writing people. Would you decide not to put a space before a parenthetic statement(obviously not)? Or like one comment suggested, you would never put a space after the opening or before the end ( unless you are just being ironic ).
It doesn't matter how you think it looks, it matters that you are trying to be different for the sake of being different. Stop it.
I tend to worry about whitespaces in/around if statements only when the condition is complex. SO I tend to have "if(a==b)", but maybe "if( (a==b) && (c==d) )" and may have space between the 'if' and opening parenthesis when the condition is so complex to be multi-line (but then again, at that point a refactoring is needed/natural)
I don't recall which I do, but I do know that I use less space in general nowadays than I did before syntax highlighting was basically everywhere. Anyone else change their style due to syntax highlighting?
Hell no... looking at code formatted like that makes my eyeballs bleed and leaves me huddled in a corner, with a ghastly, haunted look in my eye, as I mutter shit like "Ȋa! Ȋa! Cthȕlhu fhtagn. H'nglȕi mglw'nafh Cthȕlhu R'lyeh wgah'nagl fhtan!!" while some eldritch, unspeakable substance oozes down the wall...
And do you also add the space before the paren when you declare a function? I ask because a conditional block is often closer syntactically to a function definition than it is to a function invocation, yet I hardly ever see anyone put a space before the paren when defining a function.
I don't see that there is any relationship between a function declaration and a conditional followed by a statement block. There is no reason to use different formatting for function declaration versus invocation.