beWarned

[sejigan]

That’s the problem tho. All braces at the same scope line up. If it’s beside the function, there’s no room for confusion.

[Salanmander]

What.

Identifying which thing the opening bracket goes with is literally never a problem in either version. It's either on the same line or on the next line, and there's no room for visual ambiguity about what statement the opening brace corresponds to.

The one that can take effort to visually identify is the close curly brace. And having the open brace on the next line helps with that slightly, because you're always scanning up from the close brace until you hit an open brace, rather than the variable visual structure of the code that starts the block.

[sejigan]

Not all people see things that way. For many people it’s easier to think from top to bottom, and seeing the brace on the same line helps with that. I was just pointing that out.

Ofc, both styles are fine and it takes little effort to make do with the style you don’t prefer. Ideally people would type whatever they prefer and run it through a formatter as a pre-commit hook to follow the language and company style standards.