I prefer the new way because if you want to remove one condition you just delete the line rather than having to edit in multiple places.

I first picked up this style from the GNU C++ style guide, and it's so handy I use it in every language that accepts it.

Less likely to cause git merge conflict as you don't change the original line. You only add one.

What we need is a syntax aware git diff https://news.ycombinator.com/item?id=42093756

I agree, but I tend to find that "git diff aware syntax" also makes things simpler for humans as well

In languages where placement don't matter, like c/js, I prefer leading booleans. It makes it much easier to see the logic, especially with layers of booleans.

Personally && in the new line seems to be much better readability. Can’t wait to use some smart cop to convert all existing multiline ifs in my codebase.

For folks who scan code bases based on the front of lines, it makes it easier to grok. Also helps with deleting and inserting lines (similar to leading or trailing commas in lists).

It's funny how I have been doing this way of writing the conditions in languages, where one can, like Python (if you use a pair of parentheses) and linters have yelled at me for ages to put the binary operator on the previous line. People herald these quite subjective things like truths, just because there is some tool, that they can delegate responsibility to.