Classes for me, please.
Well, more accurately, "Base classes, please."
Give me an array of say anywhere from 4 ("fighter, cleric, magic-use, thief" a la B/X, BECMI and really, by extention, AD&D is you think of things like "druid, assassin, ranger", et al. to be sub-classes) up to...maybe...10 or 12 (if you want to consider "barbarian, druid, specialist mages," etc... their own Base class).
Adding in "Prestige/Specialty classes" is a slippery slope, imo. With the, literal libraries full of classes from splatbooks, alternate systems, homebrews found online or magazine articles, even movie or tv characters providing inspiration, allowing players these kinds of individual "classes" can really bog down the gameworld.
And, for someone like me, who works his games into a long-crafted, well-developed world setting...doing so would just wreak havoc with the world's internal consistency. I have a few I honebrewed myself. But generally, for beginning players I like to keep it to the 12 "traditional" I use.
Obviously, it's completely a DM-by-DM/Group-by-group preference, and if you're willing to crack those floodgates, that is entirely your prerogative.
But seems to me, if you can't find/mold/create/build a character concept you want when given up-to-a-dozen classes, then you're just not trying.
I recall one...not "argument", but let's say "discussion" with a player who wanted to play a "bounty-hunter vampire-slayer" type character (it was some time ago. I suspect shortly after the movie "Van Helsing" came out...2003? -04?).
Went a lil' somethin' like this...
Player: "I want to be a vampire-slayer."
DM (moi): "Sure. No problem. You could be a Ranger, or a Rogue, maybe. Even just a Fighter. Then work in [x-y-z] skills/proficiencies. You could totally be that."
Player: "But I want to be a vampire-slayer." <blank look.>
DM: <rubs temples> "You have x-number [I don't recall what was officially "on the table" back them] classes to choose from. Start with one of those and we'll go from there."
Needless to say "vampire-slayer" (as it's own class) never became an option in my games/world.
After a few pout-y sessions, all of which included at least one, "but if I was a vampire-slayer like I wanted, I could have blah, blah, blah" comment, the PC died (maybe by player choice, I don't know) and the player left the game. (I believe he'd started as a ranger -WHO, I might add, I do remember allowing to take "vampire" as his chosen foe instead of one of the "giant/humanoid races" from the list).
But I digress.
The point is, Yes, I like classes. I use classes. And I think everyone at the table (or almost everyone) benefits from having classes as a starting framework...especially beginner/new players.
Have fun and happy gaming.
--Steel Dragons