The Ribbon is good for a number of things, especially in the vertical products where there are many seldom used commands which are context sensitive (Civil3D being a prime example). Everything has its place - command line for frequently used, simple commands; Ribbon for context senstive, less frequently used tools. Don't like how the Ribbon is organized? Reorganize the panels, the tools, make your own panels and tools, hell - tear off the panels and use them as super-toolbars.
Consider is development resources as well. Microsoft provides the Ribbon as a toolkit so AutoDesk is only responsible for the implementation. Microsoft takes care of any and all updates, including compatibility with new OS releases. If AutoDesk completely managed its own UI that would require a lot of resources to develop and troubleshoot - especially when OS updates happen.
Finally, the Ribbon UI is well positioned to take advantage of touch technology. As mobile computing increases in popularity, the means of input will have to change. That boils down to a chicken and egg - do you try to fit the square application into the round mobile hole, or do you try to reshape the application before the hole is made?
---------------------------------- If you are going to fly by the seat of your pants, expect friction burns. Adopt. Adapt. Overcome. Or be overcome.