You have two computers right next to each other. You want to get a file from one to other... good luck with that. For some totally inexplicable reason, this common situation presents us with a problem that's never been adequately solved. I've seen people sitting next to each other with laptops log on to their webmail accounts to send a file. Only to find that they can't, because the file is too large. Etc.
Let's review your options:
USB's architecture means two hosts can't talk to each other.
Firewire isn't common enough a port, and there are two connector types to worry about.
Ethernet is universal, the cables are cheap, and people might actually carry them around. You no longer need to worry about crossover cables, it's the fastest external interface on the modern PC... do we have a winner?
802.11g/n is also universal. Making a peer-to-peer network in windows isn't exactly easy though, and then you have to convince the other guy to disconnect from whatever network he's on, search the area, connect to yours... several minutes of work and a huge pain in the ass.
And all of the above suffer from the problem that they set up TCP/IP connections. Even with the autoconfig addresses that you'll get after Windows gives up on DHCP, two machines connected over TCP/IP have no practical way to talk to each other. What are you going to do, set up an FTP server? Connect to the C$ share of the other machine? Even if you were to do anything like that, you'd still need to ask for the guy's IP address first. Have fun teaching Ted from accounting about ipconfig.
What we need is something that's more than just a TCP/IP connection... something that automatically discovers the devices around you and gives you the option to easily send them a file. The standard has to specify everything right up to the application layer.
So... we need bluetooth. This is exactly the kind of problem it was made to solve.
The potential of it was ruined by two factors. First is that bluetooth continues to be a $30 option (for a $0.30 chip) on a lot of laptops. Second, and more importantly, there's the matter of the windows bluetooth stack; god help us all. Make the machine discoverable, get the other guy to search for devices in the area, pair them, exchange passkeys... all through an interface that, at least on XP, confuses the shit out of everyone.
In order for Wi-Fi direct to be useful, it will have to be more than just another way to establish a TCP/IP connection, and it will have to let go of this ridiculous obsession with security: pairing and discoverability and pass keys and all that nonsense. Christ, just let two machines talk to each other.
Remember IRDA? It wasn't exactly popular, but it worked. Two computers get in range, windows makes a neat little sound, and you get a systray icon you can click to immediately send files. That's the way it should be. The one time I ever managed to use it, it was glorious.
The solution we've managed to come up with in the absence of this capability is sneakernet for the 21st century: the USB flash drive. At least they're cheap and common now... there was a time when two computers sitting next to each other really had *no* options at all. Now we have these... they're not particularly fast, you're likely but by no means guaranteed to have one lying around, and whatever disposable cereal-box prize you're likely to be using will always have just a little less capacity than you need.
Damn it, it's the future. I want to beam files from one computer to another. Why can't I?