This is a tricky issue.
On the one hand, my players like feats. On the other hand, they create problems in play (everyone has to constantly look up what their feats do, wasting time and slowing down the game). For new players, it's even more of a problem: they read that they can increase an ability score or take a feat, and they ask to see the list of feats, and in my head I'm screaming "No! It's not worth it!"
This actually applies to the Basic/Advanced split as a whole, really. In my playtest game, we have a Sorcerer, a Paladin, and a Monk, all using some pretty complex character options, and they're frustrated with how complicated the game is (and I'm frustrated when they keep asking me to look something up, since I'm the one with a laptop at the table)--but then they rebel when I bring up the possibility of using Basic options only.
I'm considering a simple table rule: If you have the PHB, you can use PHB options. If not, you can use Basic options. I wonder how much they'll complain about that.![]()
Well, I think that's the issue they are trying to address with Basic. New players should 100% start out with a basic, and even then probably a pregen. Once they learn how to play, maybe make a custom basic. Then by their third character once they get a feel for it then perhaps add the PHB AND feats.