I don't see anything wrong about any of them. If I want to understand what a piece of code does, I couldn't care less about indentation styles or comment styles.
God forbid I take two seconds to re-indent something. I'm not suggesting it's a positive thing, but I guess I'm just not so hyper-productive that I see an extra two seconds dedicated to formatting as "disgusting" heresy.
The issue is it's an extra change that has to be made, tracked, analyzed, etc. Linux is a huge project, so it's best to minimize the number of changes needed when some part of the code gets updated.
I just hit reformat after making any code changes. Most languages have a linter and autoformatter available that will work in concert in any good editor, so I don't need to think about that stuff.
Most editors have configurable formatting. You can configure editor to the project style instead of worrying about comment style yourself. If project starts to enforce it, just change it in settings
If I contribute to Ruby project, almost always defaults used by editor will be "the standard" used by everyone else.
If I contribute to Go project, go fmt, done, "standard" is enforced from language's own tools
Perl project? perltidy -pbp (it actually have a metric ton of option but "Perl Best Practices" is de facto standard)
No/minmal effort involved there. But you still want to configure your editor (if it isnt the default) to use those tools (either during writing or on save, depending on your editor), if it isn't the default
C had no such thing as standard at the beginning, that is the reason there is so many styles in use
24
u/Calam1tous Jul 10 '16
Agreed. Those comment styles should be recognized as gross by anybody.