Unfortunately a recent trend in native app design is to remove more or less essential elements, such as the menu bar. This makes it a lot harder to scan the UI looking for a particular piece of functionality: you have to guess which button is actually a menu, and which submenu of that menu the thing you're looking for is hiding under.<p>For example, Chrome doesn't have a nice and simple Bookmarks menu like FF (or Favorites in IE). You have to waste an entire chunk of vertical space on a "Bookmarks Toolbar" before you can access the button which is actually a menu, under which the bookmarks are hiding. One of several reasons I don't use Chrome.<p>There are lots more examples in Windows Vista and Win7. Take wmplayer: how do you open up a URL for streaming? It's hard to find that kind of functionality in the visible UI, because it seems not to be present. Instead, you have to use the context (!) menu on some of the window chrome (!!), and you can see that they've squished what used to be the main menu bar into the context menu. The UI actually ends up being <i>more</i> complex (it's harder to get at the features), the only "benefit" being that the application, on the surface, appears to do less.<p>Not to mention the now-fashionable ribbon toolbars, used in Wordpad and MSPaint - they've changed what used to be a <i>modeless</i> UI paradigm, i.e. menus, into a <i>mode-based</i> one with switching tabs. In many ways it feels like a step back into the 80s for me.