436 karma · joined September 1, 2007
Further, numerous studies have been done regarding lexical and conceptual semantics and the role of direct objects in semantic interpretation, and they demonstrate quite simply that whatever the direct object is of a sentence, this tends to be an affected item. Supporting a candle with a box is not affecting the candle in the ways relevant to human cognition, while tacking it to the wall, or melting it, is. So the phrasing again was misleading.
While I'm sure functional fixedness is a real phenomena, I would bet that it isn't even remotely as simple as this particular experiment suggested, and that a wide variety of linguistic techniques can affect how well people are at this. In fact, on the main page for the Candle Problem it's point out that a) using "box and tacks" instead of "box of tacks" in the instructions improves performance, while b) offering a monetary incentive decreases performance. So before you get all hyped up about how you want to think outside the box because my gosh imagine what awesomeness functional fixedness is preventing you from seeing, stop to consider that noone's got any clue what's really going on inside the mind, and you're probably just as likely to screw yourself by trying to manipulate yourself this way as you are to benefit yourself.
\\//,
Second, there has yet to be a demonstration from any known language that the language actually does not have an underlying tree structure to it — even the most free word-order languages such as Warlpiri display evidence of tree structure. NLP people may have a major bone to pick with core Chomskyan theory because of the incredibly difficult in parsing using it, but Chomskyan linguistics isn't about designing computationally efficient means of parsing sentences, it's about developing a good scientific theory about the nature of the constraints on human grammars. And I say core Chomskyan theory above because NLP people actually love various less core Chomskyan theory (Head-driven Phrase Structure Grammar, for instance, which has plenty of work done on it in the parsing world; or Combinatory Categorial Grammar which has been looked at quite a lot in the computational literature). The fact that NLP people prefer other methods such as dependency grammars doesn't say anything about the theoretical framework Chomsky introduced any more than their preference for numerical methods of differentiation and integration in mathematics bears on the theoretical importance or validity of precise symbolic differentiation and integration. Or to rephrase that more concisely — just because your computer isn't powerful enough to calculate these equations doesn't make the equations wrong.
I don't know whether or not Chomsky should be #1 on this list, but I do know that you have no clue what you're talking about with regards to contemporary linguistic theory.
For example, using English, and translating into first order logic with restricted quantifiers, as well as Ruby:
Some dog chased every cat
∃x:dog(x)[ ∀y:cat(y) [chased(x,y) ]]
dogs.some? { |x| cats.all? { |y| chased x, y }}
Unfortunately, the English sentence is known to have another reading, one where each cat is chased by some or other dog, maybe not the same one for each cat: ∀y:cat(y)[ ∃x:dog(x)[ chased(x,y) ]]
cats.all? { |y| dogs.some? { |x| chased x, y }}
Which means some poor coder might end up typing some(dog).chased(every(cat)) in his language, thinking he's getting the ∀ > ∃ reading (the second one above) and bamph, weird behavior. Even if you're familiar with how quantifiers work in this language, the similarity to english in this regard might easily lead someone to absentmindedly make this error.That's not to say that he shouldn't have quantifiers -- I think we need some interesting natural-language like things like quantifiers in experimental languages -- but it's definitely something he should watch out for.
Further, English has subject-verb agreement not subject-object agreement or verb-object agreement, hence "it is pancakes" is completely fine. Sure there maybe be some semantic anomalies, what with the singularity of the subject, the plurality of the object, and the copula which provides some sense of equivalence between them, but that's entirely a semantic issue and not a grammatical one.
Further further, setting off non-sentences by periods is common practice. You may not like it, but everyone else accepts it. You're just an idiot.
Further further further, "it's" is completely acceptable English, and isn't an official contraction only because there ARE no official contractions -- unlike French, with its (wholly impotent) French Academy, there is no authority on English, and thus no such thing as official English. The best we can do (as if we should care) is to reference the great authors of English literature (whoever they may be) and if you go by them, then you're most certainly wrong.
Further further further further, it's not your language, it's everyones, and I think the headline is fine; and they're not abusing it, they're using it in a completely standard fashion.
</actual linguist>
let a = (if a > 0 then a + 1 else a)
in #something or otherThink of all the boyscouts that will get lost without the use of a working compass! LOST I tell you!
The most obviously impactful part of the pole shift will be all the changes in migratory patterns as birds start migrating to the middle of the ocean or steppe.
More people have been to Russia than I have.
Think about that one for a bit. LL did a post on it, btw: http://itre.cis.upenn.edu/~myl/languagelog/archives/000860.h...
The phrase that follows the comparative preposition "than" is not necessarily a reduced clause. It's actually almost always a simple noun phrase, taking the default accusative case.
"I am taller than him" is Standard American. If you were to say "I am taller than he" you'll sound like a twat.
Doesn't make sense? So what. Language isn't about making sense, it's about getting points across. There's plenty more in English that's even more confusing (exceptional case marking? oh yeah, baby, figure that one out).
Hell, even if it WERE a reduced relative clause there are plausible reasons why it could still be "him", namely, "nominative" and "accusative" are structural case, not semantic case, so they get assigned depending on the assignee's position in the sentence structure, and you could easily reduce a clause and, in doing so, put its subject into precisely the structure necessary for accusative case.
Let me put it this way: If it were that easy, out in the real world, I'm fairly certain prisons would be impossible.
Keep in mind that the gatekeeper is not obliged to sit and listen to the AI-in-a-box. The gatekeeper is not even obliged to pretend it's a real AI-in-a-box scenario and make the decisions he would make in that situation; you can sit there thinking, nay, SAYING "man this is gonna be the easiest $10 i ever made" for the whole two hours and tough shit for the would-be-AI.
I continue to refuse to accept the possibility of Eliezer having won those two rounds without being paired with a completely retarded gatekeeper.
for (x in men):
if john saw x:
the_man = x
break
mary knows the_manwe can do something like
mary knows men.select { |x| john saw x }
namely, relative clauses: "mary knows the man that john saw".But relative clauses are difficult to process when they're not tail recursive (think of The House that Jack Built in English vs. Japanese, let's say).
So what it might suggest is that the brain is a functional tail-call optimized system, rather than generically imperative or generically functional. This might explain the apparent preference for imperative programming.
Bigotted asshole.