ajarmst

56 ms·

481.
by ajarmst 10y ago
Yeah, but the information erasure didn't happen when you applied double negation. It happened when you accepted a surjective convention where 5 mapped to True (and so did every non-zero value). The erasure wasn't accidental---it
482.
by ajarmst 10y ago
But surely no one believes that that particular case says anything about logical negation? It depends on the convention that "if it's not 0, it's true", which isn't even true of many computer languages, much less s
483.
by ajarmst 10y ago
Replying to myself. Roqua has a nice description of the motivation elsewhere in this thread, with regard to how a constructive proof can offer more insight into the thing being proven than a mere 'yes, it's true'. I can see
484.
by ajarmst 10y ago
I don't get it. Do they feel that ¬¬ϕ = ϕ is invalid or contingent? Or is it just a matter of taste?
485.
by ajarmst 10y ago
Ah, not the author's fault then. Just unnecessarily opague terminology in the canon. I'll redirect my irritation to his predecessors (Constructive Logic seems a much better term that doesn't do any violence to the rules of E
486.
by ajarmst 10y ago
I kept getting pushed out of flow by words like "intuitionistically" and constructions like "derive absurdity" (as opposed to 'derive an absurd conclusion'). 'Intuitive' is a perfectly functional wor
487.
by ajarmst 10y ago
I'm often baffled by why it is that Programming is one of the very few (perhaps only) academic disciplines or technical proficiencies where learning without the assistance of another, more expert, human being is not only accepted, but
488.
by ajarmst 10y ago
Adding a plug for Ratey's book "Spark" ( https://www.amazon.com/Spark-Revolutionary-Science-Exercise-... ) which is a pretty good lay introduction to a lot of the research on cognition and exercise as well as e
489.
by ajarmst 10y ago
Dave's response: https://lists.freedesktop.org/archives/dri-devel/2016-Decemb...
490.
by ajarmst 10y ago
AMD's response is 25% talking about unrelated Exynos code, 35% sarcastic complaints about Linux culture and 20% explaining why its naive to care about code quality and style. It concludes with a barely veiled threat about how they won
491.
by ajarmst 10y ago
So, if you had a few dozen pints of toddler blood in, say, a bar cooler, what would be the best way to dispose of that? Asking for a friend.
492.
by ajarmst 10y ago
While I applaud the effort, this sort of thing suffers from the same problem any "quick introduction" to something rich and complex has: it's easy to see the complexity and discern the unfamiliarity, but requires effort to di
493.
by ajarmst 10y ago
In my experience there's two ways to do it: (1) use the house style (and standard auxiliary packages) of whatever publication you are writing for and/or (2) develop your own style files that use the subset of the 'thousands&#
494.
by ajarmst 10y ago
Seems overly complex. The way I learned it, and now teach, is to read the type backwards (int const * is 'pointer to const int') for const correctness, but anything that requires more complex parsing by a human should just be typ
495.
by ajarmst 10y ago
Sigh. *rationalisation. Doesn't really help your snark when you emit a silly typo.
496.
by ajarmst 10y ago
Ah, another entry for the "I didn't read the books people say I should have---here's my nationalisation" genre.
497.
by ajarmst 10y ago
Poor Grissom gets screwed again.
498.
by ajarmst 10y ago
Be careful with that assumption: the standards for reliability and safety for crew-rated vs. uncrewed vehicles are very different. I've heard figures at around 10% hull-loss accident rates as expected for uncrewed, vs. an order of mag
499.
by ajarmst 10y ago
Demonstrative "that" adjective-connective-subjective "seems" infinitive-marker "to" verb-existential "be" verb-passive-gerund "missing" article-definite "the" noun-subject "po
500.
by ajarmst 10y ago
Unfortunately, that tends to demand the observation that C is really compatible with C.
501.
by ajarmst 10y ago
Intend in one hand, and ... well, you get the picture.
502.
by ajarmst 10y ago
That's not really fair. If you go far enough back in the ancestral compiler list on any language, you'll probably hit C. You'll definitely hit hit assembly and bare-metal machine code. Heck, at some point you might run into
503.
by ajarmst 10y ago
Exactly. If I make a claim, you don't have to pay me to earn the right to dispute that claim. "Here's a lamp. It's magic." "Uhh...It doesn't appear to actually be magic. It's not even a decent lam
504.
by ajarmst 10y ago
"Apparently after graduating from university 42% of people never read another book. Ever!" [Citation Needed]
505.
by ajarmst 10y ago
"coverage made with love, literally" Heh. I interpreted the name as reflecting a love of rage. Which perhaps says more about me than it.
506.
by ajarmst 10y ago
After-the fact probability analysis is weird, but the actual predictable risk (before Apollo 1) was certainly less than 1/12, although that's what the hindsight risk for Apollo primary crews was. Of course, it was 0 for all the cr
507.
by ajarmst 10y ago
No, but before that incident, they were operating as though it was near zero. The actual risk can't be determined by a handful of incidents (or their absence).
508.
by ajarmst 10y ago
Technically, the number of Apollo primary crew astronauts who've died of heart disease is the same as the number who've died in fires in pure oxygen environments. That's the problem with small sample sets.
509.
by ajarmst 10y ago
Exactly. There's simply not enough data to prove or disprove the hypothesis. What's the proposed mechanism? Because if you chose 7 American men born in the 1940s at random and then discovered that 3 had died of heart disease, I
510.
by ajarmst 10y ago
Emacs. And, uh, some kind of browser, I guess.

More ›