Nowadays I couldn't care less about what style is used. As long as the code is consistent and there's an easy way to adhere (clang-format, black, prettier, etc.) I'm happy.
The only style there that is actually used by a person is the Bourne style. There are other styles that people develop for themselves, for example there was some Haskell program posted to a mailing list with a warning about personal style. This defines:<p><pre><code> (.) :: a -> (a -> b) -> b
x.f = f x
</code></pre>
And then the author can write e.g.<p><pre><code> x.length
</code></pre>
Instead of<p><pre><code> length x
</code></pre>
I think this is really quite a natural operator (and other languages support it, eg in F# it is pronounced |> and closure has something like it with ->)
The best coding styles are the ones that allow to be translated back and forth to another style.<p>It doesn't matter which style you prefer. As long as a computer can pick it up and translate it into the project standard style and back to yours again. You can simply setup git filters and live in you own style world.
Putting every single item in this on my list of "reasons to kill a motherfucker".<p>Seriously though, I find myself oddly attracted to the Python-braces style .. if only I could use it without running afoul of my own list.
I followed the link to the OOPS source code from the comments: <a href="http://people.idsia.ch/~juergen/oopscode.c" rel="nofollow">http://people.idsia.ch/~juergen/oopscode.c</a> (originally from <a href="http://people.idsia.ch/~juergen/oops.html" rel="nofollow">http://people.idsia.ch/~juergen/oops.html</a>)<p>Aaaand… “we're achieving levels of nerdery that shouldn't be possible.”
> Poetry... quite eye-pleasing<p>I disagree with this comment. That style makes the code extremely hard to follow, as there's no proper indention to identify scope.
Kevlin Henney gave a talk ( <a href="https://vimeo.com/97329157" rel="nofollow">https://vimeo.com/97329157</a> ) that included an interesting idea for style:<p>Imagine every non-whitespace character in your code were replaced with garbage. Indent so that the reader could still understand the structure of your code.