That's pretty short-sighted. These "easy" problems are stepping stones to much more difficult problems. For instance, you cannot tell a machine something like "build my website" without it being able to solve the easy stuff first.
Oh, but the result is not what you want? Even when communicating with a human, you need to provide some specs, right? But then, natural language is way to imprecise and open to interpretation, coupled with the fact that people don't really know for sure what they want, so even when speaking with a developer, you're going to go through several iterations. So for the ultimate flexibility and automation, the user interface of such a smart appliance will end up being essentially a programming language (being the same reason for why lawyers and mathematicians have their own language that's anything but natural).
Truth of the matter is, computers answering to commands aren't really that interesting, as they already do this. What we really want are computers capable of ideas.
Also, natural language processing is hard because it's based on an incredible amount of implicit context that life taught us ever since we were born and when communicating to our fellow humans, it's never about just the actual words being spoken. When saying something like "build my website" your spouse probably knows you're talking about a website meant for marketing yourself and she probably knows your tastes and values too; she observed your fears and dreams while living your mundane life, even if you've never talked with her explicitly about such issues (speaking of women, they are incredibly good at reading between the lines).
Solving natural language processing is basically akin to creating sentient beings.
No; when a client asks me to build them a website, I don't demand a specification. I interrogate them in regular natural language about each thing, until I'm reasonably sure which things they care about being a certain way (I'll make those things that way to the best of my ability) and which things they don't care how they end up (I'll make those things however I "like" to make them, or randomly if I have no opinion either.)
I think the one thing we're lacking in software UX right now is the concept of a dialogue--you and the computer both asking questions to clarify your mental model of what the other agent currently has in mind, and adding facts to correct misconceptions until those models are aligned.
As fas as I understand the history of AI research, people have also searched for their keys in the dark. They just haven't found them.
AI that can do things we can't easily do: that's for building Multivac.
AI that can do things we can easily do: that's for building Asimov-style robots.
Does anyone know the precise quote from Dijkstra?
Finally, to correct the possible impression that the inability to face radical novelty is confined to the industrial world, let me offer you an explanation of the continuing popularity of artificial intelligence. You would expect people to feel threatened by the “giant brains or machines that think”. In fact, the frightening computer becomes less frightening if it is used only to simulate a familiar noncomputer. I am sure that this explanation will remain controversial for quite some time for artificial intelligence, as a mimicking of the human mind, prefers to view itself as being at the front line, whereas my explanation relegates it to the rearguard. (The effort of using machines to mimic the human mind has always struck me as rather silly. I would rather use them to mimic something better.
“The question of whether computers can think is like the question of whether submarines can swim”
I don't know about "best", but solving problems that a person can solve will increase the standard of living and create immense economic growth, because solving problems that only humans can solve means that more human work can be automated.
And then there is doing stuff that isn't easy for humans that requires at least the same level of intelligence. Like engineering things or writing computer programs.