I read an opinion that argues for using Entity Reference to content types as a complete replacement for Taxonomy, on the basis of UX and performance. The UX issue appeals to me - happy content managers (who don't have to go dig around in Taxonomy ever) is important!
In considering this strategy for a new site that will be essentially built around one content type that can be tagged lots of different ways, I have a couple questions:
- Is there really a performance difference? Can it be quantified?
- I need hierarchy support. Is there a good option? Searching around, the land of Entity Reference hierarchy options exists but seems like a wild west at this point.
- Are there better solutions if my only complaint is site admin UX?
- Taxonomy is the best-practice, as it is in core, for the general use case. I'm wondering what else I haven't considered in going off the beaten path here.
(Note a very similar question has been asked before, but it is talking about using Entity Reference to taxonomy terms, rather than replacing the Taxonomy module. I also understand the purpose of Taxonomy, but am wondering what would make alternatives worth considering.)