Discussing the (Im)Possibility of Natural Languages for/in Computer Software Programming

What do you get when you "natural language" with the following commands?

Please note these these are for educational purposes only to reflect language ambiguity. Also, these examples below might not be programming language specific, but they do illustrate ambiguity in technical language and the need to watch jargon when addressing a lay audience.

• Bring the port up to speed

• Kill the user's functionality online

• Unload the backup disk's files into the stack

• Stack the hard drive with dat files

• Fix the RAM...Cap Ram on both sides

• His hardware is at peak performance

IBM's Watson Computer

Some of you might have seen these commercials for IBM's Watson computer that competed on Jeopardy last year (2011). A special thing about Watson is that it answers questions asked of it in English sentences. It uses massive parallel processors to quickly find answers to Jeopardy-like questions.

Because this is a new technology, I risk being premature with my critique, but has that ever stopped me? Although this computer is a technological marvel, I think it's being oversold as a "thinking" machine. Jeopardy contestants are humans, of course, but they are simply recalling trivial information to answer questions. Recalling vast amounts of information is impressive, but it is situational--it depends on the system's parameters or what the rules happen to be. Knowing trivial information certainly isn't critical thinking or using information to solve a problem or address a concern.

Anyway, I'm withholding my awe of IBM's Watson computer* until it does something uniquely different and not just faster. Faster is beneficial in certain venues, but it isn't any paradigm shift or revolution.
*Note: this link takes a while to load.