[FORMATTING RULE] Stroustrup / Allman / K&R

[NoxFly]

I didn't find a rule that allows me to change this behavior.

It's a subjective opinion but I find the code clearer when using Stroustrup rather than K&R, and K&R is the current (non-customizable) behavior of Biome when formatting my files.

That would be really nice to see this rule as part of Biome, it's something that I find is really missing to this tool.

[siketyan]

See https://biomejs.dev/formatter/option-philosophy/

[NoxFly]

Biome’s philosophy of minimizing configuration makes sense and is one of the project’s strengths. I support the idea of avoiding micro-style options that fragment codebases and provide little value. However, I believe brace style is a fundamentally different category of formatting — one that affects structural readability, not superficial aesthetics.
Brace placement is not a cosmetic preference; it is a structural convention that directly affects how code is read and mentally parsed. Ignoring this difference forces a single visual model onto all users, even though multiple legitimate styles have coexisted for decades.

Macro formatting influences how developers visually parse code at a glance. Unlike commas or spacing, brace placement changes the vertical rhythm and shape of code. Because of this, different brace styles have developed into legitimate, long-standing conventions across languages and communities — much more than cosmetic preferences.

Entire communities, style guides, and codebases are built around different brace conventions. Refusing configurability here does not create unity — it creates frustration for users who are asked to abandon deeply established and cognitively meaningful patterns.

If Biome’s goal is to avoid fragmentation for arbitrary details, this proposal is aligned. But refusing configurability for a structural formatting convention — one that is already fragmented in the real world — creates a rigidity that goes beyond pragmatism. This would prioritize ideology over developer experience, which I don’t believe is Biome’s intent.

Allow different brace style is not bikeshedding.

This would further increase Biome’s adoption by removing one of the few remaining blockers for some developers and teams.

IMO, I really think and hope that Biome can become the reference in the next few months or years, because I find it really easy to setup and use, is really fast and lightweight, which should be the case of any formatter and linter.
I'm not going to go back to ESLint / Prettier, after all these years of use, but I must admit the lack of flexibility for this structural rule frustrates me.

[iOSonntag]

This needs way more attention IMO, K&R is a fragment that purely exists out of an era with small displays and the need to put as much code as possible on a PowerPoint slide.

I prefer Allman style for example, and many in our company do; for us, it makes much more sense and is a lot more readable. This framework is closing its door for us with such a strict decision. I like the general approach but this is sadly a blocker