My point was that we need guidance IN THE CHARACTER CREATION SECTION OF THE BOOK so that that new player isn't left deflated.Here's the scenario all these arguments keep missing:
New player (not a hypothetical -- this is from my own table): "I want to play a Witch."
Me: "Uh, there isn't a Witch, per se, but we can hack one together using Wizard or Druid or Warlock or Sorcerer."
New player, deflating: "Oh, um, never mind."
All of the people saying "we don't need a Witch class, because all of us who don't want one would just use our system mastery to hack one together" aren't getting that you aren't the target audience. The giant world of people who don't play D&D, for whom "Witch" is a much more concrete concept than "Druid" or especially "Cleric," want and expect "Witch" to be a thing in the most popular fantasy RPG around.
If a generally non-offensive Druid can be in the PHB, a generally non-offensive Witch can be. A core class is doable -- there's plenty of mechanical space left in the game for another caster, probably multiple sorts -- but a subclass is undeniably doable, especially if the cross-class subclass system makes it into a future PHB or other book. (And yes, the Witherbloom is a great start at that, but again, when someone says "I want to play a witch," they don't want to be told "just pretend this Witherbloom in a supplement about MTG is a Witch.")
We need a way to present that witch archetype with the tools already existent, much like how we need to present the Warlord concept.
The term Witch is really popular because it means so many different things. The correct answer of the DM would be to ask "What kind of witch do you want to play?"
And then say "oh, that's called a Druid in this game book, but it's totally the same thing." The book should have that guidance.
What we DON'T need is another class that steps on those classes toes. Maybe in a hypothetical game built from the ground up a Witch class would work, but we're talking about implementation into a roster of current classes where a witch class would just create more confusion regarding the overlap. The classes need to be incredibly distinct.