The new command line is closer to a textual representation of the GUI: it rewards imprecision and ignorance, and trades intuitive correctness 95% of the time for impossible obscurity the other 5% of the time. And it's verbose: "List all the files in my current directory that in in '.txt'" isn't nearly as nice as "ls \ .txt". Do we really need ad-supported fluff from Google, Yahoo, and Microsoft, when we still have ba…
But... What if the command line interpreter gets smarter and understands concepts within your query. "Find all articles last week that mentioned Ycombinator" for example. Machine conceptual awareness will be a big thing on the internet, but it is a HARD problem. We will then enter the world of Find engines instead of search engines.
Been taking precisely that approach for some time thinking through and trying to create a CLI with recognition. The novel approach consisted (I've since stopped working on this particular problem) of an interface that interacted with some known commands, applications and data.
The more you type into the machine, the more it recognises certain things related information names, associated projects, that appointment you have for next week, the document due next week. The crux was realising that meaning could be attained from small SMS like messages. A message could consist of peoples names, times, predefined commands. Then trying to weave some sort of context within related messages.
The big problem is the contextual awareness. NLP is one way to go, but recognition without having to annoy the user with confirmation is difficult. Recognising language is a big ball of string. One promising approach is to add a Adventure like shell interface onto the front, pre-describe (or dynamically build) the space you can navigate. This means your using a human brain to augment the system offsetting having to use the brute force approach. Then integrate with back-end applications.
Sounds good in theory but I agree it is HARD.