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 -
Since LLMs are all anyone can talk about...
I've been messing around in some experimental projects ahead of my new job starting. A thing I may have to do is upgrade some .Net Framework projects to .Net 10. It turns out Microsoft has actively broken every means of doing this except to use Copilot. There used to be a .Net Upgrade Assistant but it's been deliberately broken in new versions of Visual Studio. So copilot it is I guess.
It generated some very nice looking assessment.md and plan.md files, and generally walked you along, giving you the exact prompts that were valid at each step of the process. And that's about the last nice thing I can say about it.
The first thing that went wrong was after generating the plan.md file, I guess it forgot what it was doing, and prompted me to start a new @modernize prompt, even though I was already in one. Well, whatever. That new prompt found the old plan.md file and just picked up where the other got confused and forgot what it was doing. It very quickly said it was finished, and the project built and passed all the unit test.
It had actually done nothing.
When I point this out, it cheerily began actually updating projects. After probably an hour of it thinking very hard on each one, and needing constant reassurances to continue, it claimed it had finished, all projects build, and they pass all test.
This was another lie.
But it had gotten far enough along that I could manually fix the remaining issues (mostly package versioning issues it claimed it had already fixed), and viola, my simple solution with about 8 small projects was upgraded from .Net Framework 4.8.1 to .Net 10.0. Hurray! Only took me all afternoon babysitting an LLM that lied consistently, followed by manual touch ups.
This morning I discovered there is actually a CLI tool. It's no longer supported, but using that took me about 20 minutes. It still flubbed some thing, and bafflingly upgraded several projects to .Net Standard 2.0 instead of .Net 10 despite my specifically telling it not to. But that's just editing a value in the csproj file after the fact. Oh, also telling it to analyze any of the projects consistently crashed. But all in all I think it did a better job than Copilot.
I sure am glad RAM prices have gone up 3-4x for this!
While AI has many issues, and is very far from perfect, I do need to rise to it's (limited) defense.
Copilot is BY FAR the worst AI system I have used. It lags so far behind ChatGPT/Claude/Gemini (or their respective CLI agents) it's kind of mind-blowing that it was made by an American tech company at all.
Copilot was the only AI we had at work for a while and it was genuinely faster to use Google AI studio with anonymized data/to make generalizable frameworks to then use on client files by hand than to use copilot for anything.
Seriously copilot is so bad I genuinely believe, given it's such a huge % of people's AI experience, that it is in very large part responsible for people not taking AI as seriously as they should.
Copilot is so bad, don't use it.
I don't consider MIcrosoft and American tech company anymore.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link