I am not clear on the internals dealing with "tag" , but in your
example I guess the tags needs to be associated with classes, but our
current "tag"s are associated with a packages?

Yeah at least to me it feels that it is associated more with packages.

GT-Tests-Spotter makes a good example, tagging classes as: Exceptions;
Scripting; and Mocks. You might simultaneously have filter categories:
��* Exceptions
��* Scripting
��* Mocks
��* Exceptions,Mocks
��* Scripting,Mocks

To me this seems like unreasonable amount of extra effort and shit ton of cognitive load with no obvious benefit.

Sure, tags are powerful in theory; but to make them work you need to apply them consistently throughout the whole system to get the benefit.

_For me_ this seems like unproportinal amount of effort with little gain.

E.g. Gmail allows to tag emails, yet I treat it very hierarchically; that way I there is always only one way --- the most meaningful of them to get to it; otherwise I would have to think about all the various contexts in which it could be accessed.

So getting back to Pharo's tags, I like the fact that there are some common namings, such as many packages will have tags like "Examples", or "Tests", however I still fail to see why would you want to put one class into multiple tags and what the benefit would be.

Peter