I voted for menu driven, but that was before I read Merric's post carefully and had only read the question. The question was: do you like archetypical chargen vs. menu driven chargen, but the question should have been, based on what it looks like he was really asking, do you like classes or point-based chargen.
I like classes. I don't like narrow, restrictive, or too few classes, or classes that aren't sufficiently "toolkit" in their approach. The ranger, for example, is a bad class because it doesn't really meet many people's idea of the woodsman/hunter archetype, and it's not sufficiently well set up to be anything other than a spellcasting, combat style weirdo.
Now it's not that the ranger is a bad class, it's just that there's no sufficiently menu-driven class that meets the woodsman archetype in a variety of different ways to suit the taste of the player. In other words, I don't want WotC to tell me what the archetype is all about and how to play it, I want them to facilitate my own interpretation of the archetype. To use the ranger as only one single example (I could do the same with several other classes.)
Conversely, a good class is the AU Totem Warrior, which has tons of flexibility and can be built in a number of different ways, all of them subtly, yet noticably, different. It's meets an archetype broadly, but it is a very menu driven design philosophy.
Of course, the other method is to add a lot more core classes. I guess with the Complete line of books, that's even official (although I'd been using stuff from d20 publishers to fill that gap already). That way you have lots of narrowly defined archetypes, but there are lots of them, not just a handful like the core rules have.