Quote - > Quote - They're not ego folders. They're called "controlled namespaces".

Imagine the grief you'd have if every vendor who made, for example, an evening gown called it "Evening Gown". Upon loading two different vendor's products, you'd end up trashing the one you installed first, in favor of the one you installed last.

By creating an eponymous folder above the product, such collisions are completely avoided. (Assuming no two vendors have the same name, which is pretty likely.)

Which is great if you don't actually have very much in the way of content.  Some of us have 1st world problems, i.e. runtime collections approaching half a terrabyte or more. - for us, ego folders are one (of the many) banes of our existence.  From something I wrote last year:

 

An easier solution is naming a product Evening Gown by .  The vendor gets their ego stroked & the customer can actually find something.

I have zero interest in letting vendors organize my runtime for me. But then I pretty much manually unzip my downloads instead auto zipping them to where they're supposed to go. DAZ is pretty much the only exception to that rule because of their installers. But it sounds like you, Bryan needs to break down and reorganize your library. If you need to break your library up into categories like Swimsuits, Mini skirts, Lingerie and Evening Gowns. Then the vendor list for each category will be less wieldy.