That is matter long resolved in my opinion with the change in the default search namespaces that the communities made, and similarly with our redefining content namespaces. While main namespace will always take preference to the other nss in results, they show up pretty quickly where you have an intitle: match.
At enWS I would say that we lost more searches to subpages, so with the ability to change your search preferences with subphrase matches, much of that is addressed (though it is not the default search configuration at this point).
Corrects up to two typos. Resolves close redirects.
Corrects up to two typos. Resolves close redirects. Matches subphrase in titles.
No typo correction. No accent folding. Strict matching.
No typo correction. Resolves close redirects.
No typo correction. Resolves close redirects. Matches subphrase in titles.
From afar, the Opera: pages on it.ws are very close to the pages with the template {{Éditions}} on fr.ws or the template {{Versions}} on en.ws (and similar system elsewhere).
The main difference is having a separate namespace A second major difference is that the templates on fr.ws and en.ws are very light while the {{Opera}} template took data from Wikidata (but that's an independent problem, it's possible to change the {{Éditions}} or {{Versions}} templates to do exactly the same thing without having a specific namespace).
I'm almost convinced too, but in order to create a new namespace on a project you have to convinced the local community. That's why I'm still playing the Devil's advocate role and want to learn about the inconvenients of this system
A reason why there are no different namespaces for work-, edition-, author-, list- and other portal pages in de.ws is the ws-search. When you are looking for "Goethe" in the (simple) search (as readers may do) on WS, you might get to