Who knew.
Not using hamburger menus doesn't magically make your app better. You need alternatives. Would I suggest a hamburger menu for a menu with 3 items? No of course not. But if you have an app with 10 core menu items, there's not many alternatives. You could try to force and cram that into a navigation bar with 3 item-categories, which open pages with deeper navigation trees, and that'd tick all the 'why-not' boxes of the menubar the article mentions (like unnecessary clicking, users that can't find their information, don't know where they can go or where they are on the page etc etc).
Fact is that a lot of users are indeed familiar with hamburger menus these days and they're becoming a type of standard just like a back arrow is universally understood, and find their way outside of apps, too. (like the Chrome browser which I'm typing this on right now.)
Combine that with the fact the top navigation bar's title telling you where you are, and a non-crammed side menu showing you exactly where you can go, it's certainly a decent solution for many apps.
Also, if you enable it, it automatically allows users to choose which tabs that goes where, just like in the music app :)
I haven't heard the the term "hamburger menu" until now. That's a pretty condescending term for a UI widget that looks visually pleasing (to many people).
For what it's worth, this is what I have been using: https://github.com/erichoracek/MSDynamicsDrawerViewControlle...
If they would feel the same about the hamburger menu, then they'd do the same.