nixCraft 🐧Let us set the record straight: which one are you? foo() or bar() and why?
josejuan@nixCraft I am the one who writes both.
nrcha
flere-imsaho 🇺🇦def foo():
[…]
Appendix2735 🐧@nixCraft definitely foo(), It just comes across as so much cleaner to me
David Senk@nixCraft oof.
Depends on the language and standards of the rest of the code base for me…
I usually prefer 1, but 2 is sometimes a bit easier to read.
Colored brackets in the IDE are great though, makes is so easy to see what’s paired to what.
Ertain@nixCraft I would prefer `foo()` since it usually leads to stuff like "bar" or "foobar".
Nebraska Jones
Greg Ar Tourter@mctaquitos @nixCraft yup, same here!
Chris :: IO ()@nixCraft I am team stick to the coding conventions of whatever language I am using atm
avatastic 
@nixCraft it depends on language, and how incorrectly I'm remembering the style guidelines.
Sterling@nixCraft
bar() .... it's just clearer to me.
bar() .... it's just clearer to me.
ϻค𝔬ᑭ@nixCraft
Depends on the language each one has its own coding style, some allows you to do what you want, others like Go will give you an error if you dont put the brackets where 'it belongs'
I only care that the style is consistent in all the project
Charlie`foo() {` definitely. Seeing just a random '{' on a line by itself seems off for some reason.
When more arguments are needed for the acceptable line width,
`foo(
...
) {`
petur 😶🇺🇦🇵🇸🇹🇼@nixCraft bar() sorry
IllusiveProgrammer@nixCraft doesn’t really matter to me. I usually write foo but if the editor I am using switches it I am fine. Or, if I’m working for or with someone that prefers one or the other I am fine. So many more important things to use your brain cycles on.
リーハイ@nixCraft Whichever the style guide recommends, otherwise I'll use the general consensus for the language. That is, for C and Perl I use method 1, but C++ and Java I use method 2.
Jaakko Nissi@nixCraft I've always preferred waldo. It's fun to play "where's waldo" with a codebase you haven't touched in a couple of months. 😅
Mackajfoo() 80%
bar() 18%
doo() 2% (for those💡moments)
iXô 
@nixCraft bar, I prefer when the symmetric way of having { and } aligned. And that’s why I don’t really like Go that force you to have { at the end of the line
v̾i̾t̾r̾i̾o̾l̾i̾x̾@nixCraft neither, it should be
void foo() {
// code here
}
Infrapink (he/his/him)@nixCraft
foo() because I'm not wrong.
foo() because I'm not wrong.
yetzt@nixCraft /* comments */ for code, but
// for annotations.
// for annotations.
JJ Celery@nixCraft I'm baz( ) 😉 which means foo( ) but my closing bracket has same indentation as opening bracket.
Everything else is wrong .
Budley@nixCraft in C,
void
bar()
{
}
Function name is always bound to the beginning of the line, braces always align.
Mark Sharp@nixCraft I tend to go with the coding standards of the framework I work in. Which is usually inline. However. I have a strict aversion to the whole foo bar thing. Utterly meaningless.
ⰎⰅ ⰀⰍⰨⰒⰎⰫ
ADM@nixCraft Method 1.
void foo() {
/* code */
}
Because a professor in college once told me that method 2 is used in college textbooks as a way to make the book longer and therefore more expensive. And that stuck with me.
But if we're being COMPLETELY honest....
def foo():
pass
@nixCraft foo; why waste another line?
Arnaud Launay@nixCraft Team bar. At least they have drinks.
🪨@nixCraft foo is java, bar is c#
Ralph is verhuisd@nixCraft I like Foo Fighters, not bar fighters.
Myza Nil Red
mil@nixCraft I used to be bar() until someone inserted a statement between head and body, thus drastically changing the code. now I prefer to foo()
aquaratixc 
Brian Shaw@nixCraft Definitely 1, but with a space between () and {