Be advised: this thread is not for serious in-depth discussion of weighty topics (we have a link for that), this thread is not for anything Culture War related. This thread is for Fun. You got jokes? Share 'em. You got silly questions? Ask 'em.
What is this place?
This website is a place for people who want to move past shady thinking and test their ideas in a
court of people who don't all share the same biases. Our goal is to
optimize for light, not heat; this is a group effort, and all commentators are asked to do their part.
The weekly Culture War threads host the most
controversial topics and are the most visible aspect of The Motte. However, many other topics are
appropriate here. We encourage people to post anything related to science, politics, or philosophy;
if in doubt, post!
Check out The Vault for an archive of old quality posts.
You are encouraged to crosspost these elsewhere.
Why are you called The Motte?
A motte is a stone keep on a raised earthwork common in early medieval fortifications. More pertinently,
it's an element in a rhetorical move called a "Motte-and-Bailey",
originally identified by
philosopher Nicholas Shackel. It describes the tendency in discourse for people to move from a controversial
but high value claim to a defensible but less exciting one upon any resistance to the former. He likens
this to the medieval fortification, where a desirable land (the bailey) is abandoned when in danger for
the more easily defended motte. In Shackel's words, "The Motte represents the defensible but undesired
propositions to which one retreats when hard pressed."
On The Motte, always attempt to remain inside your defensible territory, even if you are not being pressed.
New post guidelines
If you're posting something that isn't related to the culture war, we encourage you to post a thread for it.
A submission statement is highly appreciated, but isn't necessary for text posts or links to largely-text posts
such as blogs or news articles; if we're unsure of the value of your post, we might remove it until you add a
submission statement. A submission statement is required for non-text sources (videos, podcasts, images).
Culture war posts go in the culture war thread; all links must either include a submission statement or
significant commentary. Bare links without those will be removed.
If in doubt, please post it!
Rules
- Courtesy
- Content
- Engagement
- When disagreeing with someone, state your objections explicitly.
- Proactively provide evidence in proportion to how partisan and inflammatory your claim might be.
- Accept temporary bans as a time-out, and don't attempt to rejoin the conversation until it's lifted.
- Don't attempt to build consensus or enforce ideological conformity.
- Write like everyone is reading and you want them to be included in the discussion.
- The Wildcard Rule
- The Metarule
Jump in the discussion.
No email address required.
Notes -
Which indentation style do you prefer?
IMO, Ratliff makes the most sense, because it's the only style that reduces the number of tabs after typing the closing brace, rather than before.
I find it disconcerting and nonsensical for the IDE to automatically delete a tab before the cursor when the user types a closing brace in non-Ratliff styles. Also, I'm not much of a programmer, but I imagine that writing a program to pretty-print code in non-Ratliff styles must be a major hassle, because it would force you to move the cursor backward and then forward again after finding every closing brace.
I don’t understand why more people don’t recognize that Allman is clearly superior.
If you get paid by the line, then it certainly is.
More options
Context Copy link
More options
Context Copy link
K&R, accept no substitutes.
It's logically consistent, space-efficient, orderly and readable. The others don't even come close.
While Visual Studio and C# are my drugs of choice, the worst thing about them may be the default linter & style guide's insistence on Allman.
K&R has always been the best, and as you say, it's not close.
More options
Context Copy link
More options
Context Copy link
I prefer K&R with mandatory braces around single-statement blocks.
More options
Context Copy link
Whatever the linter thinks is ok
More options
Context Copy link
There's a saying "code should be written to be understood by humans first an only incidentally executed by a machine".
None of them are actually harder or easier to read, it's just a matter of familiarity. You need to train your brain to quickly parse code and tweak that for new indentation styles.
You're going to have a better time if you just learn to read the most common styles quickly. You're inevitably going to be reading a lot of other people's code.
I like otbs. It's K&R without skipping braces on one liners, which can lead to bugs on a messy merge.
More options
Context Copy link
This looks very wrong to me. Closing brace being at the same indentation as the start of the block is what makes sense to me.
This is my preference, but I'll work in whatever the code base I'm playing in already has.
More options
Context Copy link
Agreed. I also prefer two spaces of indentation to four, four is just such a waste of space for (imo) no readability benefit.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link