You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
2So true. Life is too short for manually formatting code. More cost efficient to let automation do it.chux– chux2024-05-29 17:10:11 +00:00Commented May 29, 2024 at 17:10
-
Yes yes, but remember, someone has to write those tools.candied_orange– candied_orange2024-05-31 11:17:44 +00:00Commented May 31, 2024 at 11:17
-
It's not true that styles are equivalent, even if you have enforcement. Vertically coupled alignment leads to larger commit diffs, more merge conflicts, poor use of space and inconsistent source code density. Also, a nit: you want automatic application of a style, not just enforcement (e.g. commit blocking or merge blocking) which is a huge inconvenience.Dave Abrahams– Dave Abrahams2024-11-07 17:42:54 +00:00Commented Nov 7, 2024 at 17:42
-
@DaveAbrahams I'd rather have a codebase that was consistent, and a tool dealing with it, than have the "perfect" style as applied by each dev. Once you have a tool enforcing it, it's really easy to have buy-in for a tool applying it. Different people will have different preferences as to when that tool runsCaleth– Caleth2024-11-08 09:16:28 +00:00Commented Nov 8, 2024 at 9:16
-
@Caleth I have no argument with that. I'm not saying which style you choose is more important than enforcement (although I maintain that mere enforcement is much worse than automatic application, and might even be worse than no enforcement). I'm simply addressing the idea that what style you choose doesn't matter at all. There are objective factors that make vertically coupled alignment worse than other choices.Dave Abrahams– Dave Abrahams2024-11-10 16:45:57 +00:00Commented Nov 10, 2024 at 16:45
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you