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.
- 65
- 1
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 -
Due to what is likely a legislative error, the [Canadian] government deleted privacy safeguards that were included in the bill only two months after they were enacted. As a result, a provision stating that the Broadcasting Act “shall be construed and applied in a manner that is consistent with the right to privacy of individuals” was removed from the bill, leaving in its place two-near identical provisions related to official languages.
I'd say it's time for us to join the 20th century, but apparently Git was first released in 2005.
Wikipedia had diffs long before that. There were also older source control systems, but they tended to focus on tracking files instead of tracking sets of changes to multiple files.
The Canadian legislation process was pretty archaic back in 2010 or so when I had some direct knowledge.
The House of Commons, the Prime Ministers Office, and the various ministries are all involved in drafting legislation and all have their own completely separate IT systems. Their IT departments disabled all of the collaboration features outside of their individual Microsoft Domain for "security". All collaboration was done by emailing full documents or reading changes over the phone.
So screw ups like this will naturally happen. Of course it's entirely possible that someone did it on purpose.
Older verion control systems tracked changes all right, but they didn't have a good diff-merge mechanism. In something like SVN you would normally check out a file, leaving an exclusive lock on it, modify it, then upload the new version and release the lock. The system would track the difference as a reverse diff to save space, but wouldn't really let you merge two diverged histories like git does.
SVN of course had a diff merge mechanism, and one person checking out a file didn't prevent others from working on it. The checkout happened in your local copy of the central repo. When you committed, your changes are immediately sent to the central repo and you must resolve any conflicts at that time.
The difference with git is the diverging histories you mention - subversion does not allow you to have a chain of commits that diverge from the central repo that you plan to reconcile later. It has to be reconciled at every commit.
More options
Context Copy link
I met a guy at a meetup who's contracting specialty was using CVS (Concurrent Versioning System). Specifically he specialized in helping out companies who tried to use the branch feature in CVS and had screwed up their repo.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link