Which are you?

Which are you?

Right. I never understood why people like the left

if condition:
statements

150 IF Condition THEN statements ELSE anotherstatements

if
(condition)
{
statements ;
}

If I had to say, left, although is miles better.

Left side because work conditioned me to it

I was right until I joined a team that does left. I hate left. that being said I'm still right when doing personal projects, I just work a lot more than I don't.

These are among the two most popular coding standards. The first is called Allman, whereas the second is (I think) called 1TBS.

Allman is the go-to standard for C# whereas the other is used by Java.

func (
condition1 ,
condition2 ,
condition3 )
{
//do things here
}

>tfw Sup Forums gets political

$penis_large = is_nigger($jamal) ? true : false;

Fuck your shitty operators

second is either K&R or 1TBS

>implying those who pick left are people
in all seriousness though, it doesn't matter
but right doesn't just plop a whole extra line with just a curly brace on it for the beginning of a block even though the block statement it's attached to is already enough of an indicator

you're sick

...

kek

but that's uniform and readable, not pajeet enough
I have very serious issues

I could actually come around to this I think

i
f
(condi
tion)
{
statements
;
}

cond({statement
;s}})
ition if

condition && (() => {
console.log("Hello, SoyBois!")
})()

...

Left is for fags.

They don't matter, only brainlets care about which one people use

if(condition){statement;}

best

This. Use whatever makes the linter stop bitching at you, that's what. The point is that everybody uses the same linter and is consistent.

tabs all day

but what if
if(statement;){condition}
?

the world may never know

left for functions and loops. Right for chaining if statements.
I am Baphomet, who sits between the pillars

the epitome of cancer in software engineering

I had a prof who did
if (condition)
{
statement
...
}


god it was annoying reading anything he wrote with more than one or two levels deep

I would kick your asses if you did that working with me

~autism~

I hate the left.

Me too, in more ways than one

I was left when I first started programming, now I'm right and I hate left.

ha

right

habit i suppose

>comment after the code

what the fuck

i
f
(
c
o
n
d
i
t
i
o
n
)
{
statements
;
}

if (condition) statements

Admittedly I'm new to programming but I've been doing this

>t. r*ddit

#define CHECKNDO(X,Y) if(x){y;}

CHECKNDO(condition, statement)

Upvote

If(condition){statement} master race reporting in

symmetry

If the whole point of the right is to not waste lines, why not
if (condition) {
statements; }

Left because I have autism and like it all to be symmetrical and beautiful

Kernel style mandates right. Gentoo uses the Linux kernel. The choice is clear.

(if test-expr then-expr else-expr)

Left?

Stop being a smart ass. If you have any idea how gentoo ergo Linux colonel works then your going to know that right is the empireically right query to this comundrum

condition ? statement : statement

Do they mean condiments?

while True:
try:
statements
except ValueError:
print('ValueError')
continue

>1-space indentation

Python doesn't have this problem.

Python has other problems

Does anyone know which one is more popular? Seems like it wouldn't be too hard to estimate by scraping github, so I assume someone did it.

I prefer right, but I don't think I would mind that much if I had to do left for work.

Isn't that the old GNU style?

yes GNU style is braces on a newline indented two spaces, block content indented an additional two. It is hideous

yeah

Right style is used by 99% of Java devs and most javascript developers as well. Even if every single C/C++/C# project used the left style it still woudn't be able to tip the scales.

Left. Makes for easy reading and debugging. Unless you like spaghetti coding I guess.

PHP recommendations is to use both.

Class
{
}

if (condition) {
}

this way they can piss off both camps equally.

This is just trolling. There is no acceptable time to do this shirt of for keks watching other devs trying to interpret your shitposting

you can clearly see where scope begins and ends, they line up

The correct one.
{

}

if ( cond
i
tion) { statements];

>always liked left better
>college prof forced right on us and docked marks for doing left
I hated college so much.

Why would they care?

Death to the non-cuddlers! There hearsay upon the Church of Ritchie will not be forgiven!

kay in ar

you bastard

A lot of programming jobs require a certain coding style, so it makes sense that a professor would teach that skill.

Some languages have styling guides that 99% of the industry follows. You'll have to adapt to the majority at some point so might as well start now.

>Not keeping all your braces in one tab

That's already been posted.

That's because you have been programming in Python and not Java or C#. Python forces you to write like that

The professor was preparing you for industry where you are forced to do some coding style that you are not comfortable with. Sounds like the college you went to (or at least the professor) was industry focused and wanted you to succeed in the job market.

Being forced to follow a coding style is one of the most useful things any programmer can learn in university.

I use the tabulation to determine scope.

I will fuck ur mothrr son of bitch

obviously Im the first type, the only correct way to write code.
if (
condition)
{
code(
variable);
}
}

both are better than just one

>using anything but the left

java pajeets leave.

ah yes, C# pajeets are much better

I like left but I am conservatist irl

>non ligature font
>Worst possible color scheme
>Meme IDE

hello Rasheed, what are you doing in Hungary?

>black text on dark background

if (codition) {
code;
more code;

if (another condition) {
some more code;
some other code;
}

code;
}


Brackets are just noise, so i tend to put them on the side!

imagine them lined up though Sup Forums screwed it up

...

Neither. Programing is for faggots waiting to train their Chinese/Indian replacement.

DATA DIVISION.
WORKING-STORAGE SECTION.
01 VARIABLE PIC X VALUE SPACE.
88 CONDITION-1 VALUE 'A'.
88 CONDITION-2 VALUE 'B'.
88 CONDITION-3 VALUE 'C'.
PROCEDURE DIVISION.
EVALUATE TRUE
WHEN CONDITION-1 PERFORM ROUTINE-A
WHEN CONDITION-2 PERFORM ROUTINE-B
WHEN CONDITION-3 PERFROM ROUTINE-C.
GO BACK.

Left. It makes it easier to find bracket pairs.

We aren't in 80s anymore to care about 80lines on screen.

You shouldn't need to find bracket pairs if you indent your code properly.