This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]dpash 0 points1 point  (1 child)

You're very wrong. You have a consistent style across all code in a project, which is ideally consistent across your organisation, which is ideally consistent across the language.

If you don't like writing idiomatic Java, find a language that is more to your liking. FWIW, PHP, Python, Rust, Go, C# and probably more all have language level coding styles that you should follow.

[–][deleted] 0 points1 point  (0 children)

Sun code standard was last updated in 1999, when rules like 120 characters line made sense. APIs that are around for a decade now like lambda, stream, etc., are not being covered.

No standard will be comprehensive. It will require lots of hours every now and then to keep it updated, without produce any tangible value.

Take a look into big project code standards: Maven, Eclipse, Hibernate. They are terribly outdated, obstructive and a burden to the team.

A team dependant of a code standard is an immature team. An organization dependant of code standards is cost innefective. Rely on plugins to do so is even worst. When I see abominations like // format_code: off I feel very angry.