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.
- 120
- 4
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 -
I believe there are a number of software devs here. Are there any Linux / C / embedded devs here that would be willing to mentor or offer some signposting for a (near) total beginner on writing what ought to be a simple single function program? By which I don't mean "make a mobile app", I mean "read this one function call from a piece of hardware and print the value to the terminal".
I've gathered a few of the concepts but I don't have enough knowledge to grasp whether they're the right way to approach the matter and whether I'm focusing on the relevant level of abstraction.
Edit: Help is being provided. Thank you Motters.
Are you writing the hardware's driver, or just a userspace program interacting with an existing driver?
I'm definitely not writing a driver, just trying to read (physically read, with my eyes) one value from an existing driver. I've got someone helping me now and fingers crossed I can use an existing library / script that I missed to get me what I need. Looks like I overshot the mark and ended up in the kernel zone.
More options
Context Copy link
More options
Context Copy link
Maybe unrelated to your needs but I believe people waste too much human resources on niche low level languages like C/C++/rust (I've extensively learnt both BTW) and could get much more proficient and expert in their job language instead, such as Kotlin which is the sweet spot IMHO.
The language wars are a CS student thing, not a programmer thing.
Good luck making a website that is any good with C or programming a microcontroller using JS.
It all makes sense when you realize the flamewars are being fought by;
CS students arguing over which program to use in their data structures and algorithms project, most of them are yet to write a program that is one any use to anyone. To them, the idea of a language genuinely being good for a specific task is still alien.
Old-timers posturing about the good ole days.
To argue that every languages are equal is intellectual obscurantism.
Of course both CS students and old timers are major tribes in that culture war but that is irrelevant to the fact that languages have objective features and merits that can be civilly discussed.
Im strongly skeptical that a vast majority of the people partaking in those wars are priviledged to the level of job security where deeply rooted perks/flaws of the language actually matters to them, relative to how strongly they feel about it.
Outside of a flamewar context where the technical details are of concern, I have no issue with dissecting languages.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link