As for the other questions answered, you're not a beta tester? I didn't realise that; I guess that's why my specific interface bug questions get ignored
.
As a developer of the applications, I'd never call myself a beta tester. We have a strong culture of "dogfood". Dogfood, like certain other words in the language, can be used as nearly any part of speech. It comes from "eating your own dogfood", the idea that the people who make the applications should use them too. It's a verb ("I'm dogfooding the latest version"), a noun ("did you get today's dogfood?"), an adjective ("it's not quite at dogfood quality yet), and so much more. I think that only the F-bomb is more flexible.
Every day, we spin up a new build. That is, we take all of the latest code that's checked in, and we create the .dmg files for Office. This happens from the very second we start working on a new version. Once the build is "dogfood-ready", the team starts to use it for their own daily use. When we're pretty early in the project, most people use both the current version and the new version under development simultaneously. The ratio of current:new changes over time. Personally, I've been using Office:Mac 2011 as my only Office application, except for a handful of forays back to Office 2008 (generally when I'm giving an external presentation and can't show our latest work), for well over a year.
Since we haven't yet announced all of the new features of Office:Mac 2011, or areas where we've made major improvements over Office 2008, I can't yet answer a lot of questions. I'd like to answer, but I'd also like to keep on paying my mortgage, and my mortgage always wins.
For now, suffice it to say that a lot of the concerns that have been raised in this thread won't be concerns in Office 2011.
Regards,
Nadyne.