I'm not sure the comparison is quite the same. The key difference is that with a CLI or punch card interface, you need to know the command syntax in advance - it can't be discovered by interacting with the system. With a GUI, you can discover the appropriate commands to make the application do what you wanted to do.
The menus vs. ribbons debate essentially boils down to one of aesthetics. But I'll personally agree with barrkel in finding it much easier to locate the function I need by browsing through one-dimensional lists of text than by browsing through two-dimensional grids of pictures (of varying sizes and shapes).
The Ribbon may make locating a small set of basic features slightly easier for inexperienced users, but it makes far more difficult for everyone else to work with more complex functions - the very thing for which software adds the most value.
Comments
I'm not sure the comparison is quite the same. The key difference is that with a CLI or punch card interface, you need to know the command syntax in advance - it can't be discovered by interacting with the system. With a GUI, you can discover the appropriate commands to make the application do what you wanted to do.
The menus vs. ribbons debate essentially boils down to one of aesthetics. But I'll personally agree with barrkel in finding it much easier to locate the function I need by browsing through one-dimensional lists of text than by browsing through two-dimensional grids of pictures (of varying sizes and shapes).
The Ribbon may make locating a small set of basic features slightly easier for inexperienced users, but it makes far more difficult for everyone else to work with more complex functions - the very thing for which software adds the most value.