For example, apps like Etherpad or Apache Wave need to send messages for each editing operation (e.g. keystrokes), and it would really suck if they had to open a new HTTP connection for each one and do long-polling to receive from the server. Websockets make this sort of thing simply a matter of sending and receiving on a socket. Easy.
You can fake them with something like Socket.IO, if you want the API and are willing to tolerate unpleasant performance on browsers that don't support it.
I'm using Socket.IO and while I'd rather not have to degrade to Flash for Firefox, if that's what I have to do to get support for Firefox users that haven't enabled websockets, I can live with it.
The only difference is that with the WebSockets the ugliness is hidden from your daily programmer via a nice API.
But I'll still going to stick with the fact that they are ugly hacks.
The API is not the only difference between HTTP and websockets. HTTP follows the request response pattern. A websocket is a pair of message streams.
People refer to it as "TCP for for the web", but it is more than that since it specifies framing as well.