e.g., the right-click menu does reduce mouse travel which is a real enough advantage, and also is more consistent with desktop conventions, but at the cost of breaking multiselection, reducing the effectiveness of visual memory in finding commands, and removing consistency between mouse and touch methods for doing the same thing.
I respect your opinion but they didn't break multi-select. It restored it to its former behavior. Hold the <CTRL> key down and click away.
Yeah, I actually think of it as a variant of the Office selection/commanding model, with the floating mini-toolbar and contextual tabs. I would prefer to see the floatie adopted everywhere (with the original "fade in as your mouse pointer approaches" behavior from Office 2007/2010), then they could maintain the mouse travel advantage of desktop context menus while also maintaining the simpler selection model, richer icons etc., and more consistency between mouse and touch layouts that the app bar commands had.
Maybe I'm old but those floating menus always get in my way. I find myself constantly hitting <ESC> to dismiss them. I left them on thinking I'd "learn" to use them.
That said I think the radial menus that the OneNote Windows Store app uses are great for touch.
I really think it's better to build around the input device rather than take the one-size-fits-all approach. Even in "touch" mode, Office 2013 isn't a great touch experience.
That seems like a lot of work to scroll (i.e. targeting the scroll bar). Maybe using <PAGE UP>/<PAGE DOWN> would work better for you than the scroll wheel? ;) (Just a bit of sarcasm there as I'm not fond of people excusing bad behavior with "you just have to learn the keyboard shortcuts")
Honestly I dislike having to use scroll bars of any kind. It drives me nuts when things like a browser is slow in loading the last bits of a web page, the scroll wheel is unresponsive, and you have to reach for the scroll bar to scroll down the page.