Python prorammers ignore this.

Oh so now we got a fucking new fight started on devRant on which line to put brackets on.
Fucking why!!??
Both conventions basically mean same thing and even no fucking ide is partial about the fact.
Stop it!

Well each team has its own rules?

For example symfony has classes and function next line and on if for etc on the same line.

Its depends on the team still and it takes probably 20 minutes to get used to it.

Enjoy it.... :'v @terraria99

@Bernarnold but they are not curly brackets

Why frig you still use you favorite hand for anything that needs one hand or when one hand is more somewhat important than other, AND you STRICTLY REFUSE to use the other for, just saying, writing?!?
By the way, i stick to same line SO FRIG MUCH but not enough for dive into that not-holy war

@hch11 yes but why fight and write crazy rants in name of bad code and wk99

@VTCoder
Not-holy war, dude

Doesn’t always mean the same thing, E.G

function test(){
return {
worked: “ok”
}
}
function test(){
return
{
worked: “ok”
}
}
In JavaScript the top one would return an object whilst the second would return undefined.
You could argue that this is syntactical but you should try to follow the language style just to avoid little oddities.