In reply to Drew Jaynes.

@Drew Jaynes,

Actually, Drew, you have just exemplified how much the core team isn't listening.

The problem isn't that those objecting to the Customizer don't have vision. The problem is that the core team think they have a monopoly of vision. Apparently, you also think you have a monopoly on deciding what feedback counts as constructive. You're wrong on both counts.

You might get to decide what goes into core. But that's all you get to decide. You don't get to say what counts as vision or feedback.

So how about actually listening instead of attempting to define the issue out of existence?

You see, many of us have a vision too. As a writer, not a developer, I don't feel qualified to talk about the Trac ticket. But I do have a vision for how I want to be able to adjust how things look on my site. Quite literally, in fact: I use a large, widescreen monitor so that I can see everything clearly. That way I need only do something once. But you want to squish me into a tiny, narrow area wwith clunky functionality where I really can't see what I'm doing. That's literally a lack of vision.

And please don't attempt to justify the Customizer with talk of what it might become. If it's going to be so great, then develop it as a plugin until it's ready to wow us all. Until then, it's just another thing I have to turn off.

In fact, here's my real vision. How about a WordPress where core isn't so peculiar that I have to ensure that, before I start using a theme, I have to remove or disable over twenty different things?

As I said, I'm a writer, not a developer. Yet the core team's vision is so strange that I currently have to check over a theme's code before I know I can use it.

That's the problem with thinking you have a monopoly of vision. It can often turn out that you're really suffering from myopia.