In reply to Peter Cralen (@PeterCralen).

Maybe I wasn't clear: I don't believe the Customizer is the way to go regarding menus. I have a conceptual resistance to Customizer being used for everything, even more if used exclusively. The first notice about this Menu Customizer merge pointed the way to eliminate the menu admin page, @valendesigns talks about a step back. I'm not sure of that.

Although a bit messy, having two ways to manage menus, I find it preferable to a unique inadequate management option. I believe the Customizer could be used to choose and position menus, not to build menus. IMHO, Customizer should stick to appearance, styles and general options, not structure and content. Menu is not appearance, it's structure and content.

So, to be clear on this, I'm critical of this process in two basic issues:

1) the way the community criticism was handled – as if it was a like/dislike or ignorance thing –, not admiting that there's a lot of people and a lot of situations where Customizer is definitely inadequate, and
2) leading WordPress project in a direction that seems to depart too much and too quickly from what has been it's evolution.

Let's face it: if a single admin screen is so many times insufficient to manage more complex navigation structures, including multilanguage sites, what's the logic of this sudden move to a more tighter and limited editing space?