I also agree, and there's a task for this somewhere in my queue.

Yes, but it's going to be tough.

I (and also some search engines) don't like this. It reminds me of those websites consisting of one page only and a few params, like www.mysite.com?page=78 . Anyway, for other actions except view, we can decide on whatever method to specify the action.

I think the hardcoded urls have been fixed, but I wouldn't recommend having the default package configured as the ROOT webapp. Instead, we should document how to make xwiki respond to the URL without /xwiki/, either by deploying the application as the ROOT webapp, or by using apache+mod_jk+URL rewriting. This is because xwiki might live in a crowded environment, where the ROOT application already exists.

The /bin/ part is needed for sending requests to struts, and the /view part is needed for sending requests to the ViewAction. XWiki works fine without /view/, what needs to be changed is the URLFactory that generates URLs. Removing /bin/ is a bit trickier, since the container must know which requests to pass to struts and which requests to serve as plain documents (what's the difference between /Skins/MySkin and /skins/default/style.css ?). But for removing the /bin/ part, we can do this:
- send requests for / to struts
- remap existing directories to a simple directory listing / file retrieval servlet. The default one should do fine, but I don't know (didn't find) a way to specify a starting directory, since if we map it to /skin/, it will serve files not from the skin directory, but from the root directory. And if we don't want to explicitly map each directory, we could have only one action ( /files/ for example) which calls this servlet, and all the problems are solved. We just need to modify the same URLFactory.