[JohnFen]

My problem with it mostly that it hides functionality. Seeing a hamburger menu gives you no insight as to what options exist under it.

The menu itself also tends to be a "grab bag" of multiple otherwise unconnected things, increasing the effort required to figure out how to do something.

[cosmic_cheese]

I like to refer to them as junk drawers due to their messy nature.

Apps with hamburger menus also tend to have navigation that’s otherwise not well though out, think burying options in chains of modals where the paths to those options change whenever the app’s dev decides it wants to push a different feature/metric.

[ryandrake]

I like the "junk drawer" analogy. It's perfect. IMO if you as an app developer find yourself reaching for a hamburger menu, that's the time to step back and stop adding junk features, especially if you're writing a mobile app or web page. If you can't fit your application's critical functionality in, say, 4 tabs across the bottom of the app, the app is probably trying to do too much.

[cosmic_cheese]

That’s often the case, but the other common problem is lack of consideration about hierarchy. It’s fine if every function of the app isn’t accessible with a single tap — that’s probably not necessary except for the app’s most pivotal functions, but most things should be able to be used within two taps and almost everything within three, with the paths being logical and predictable.

It’s plenty doable, but like I said it takes some sitting down and planning and perhaps more importantly, design centered around the user and their needs and less around looking pretty in a slideshow or trying herd the user around.