|
Cratylus wrote:
Well, what do you mean by technically superior? When I think technically superior, I think more in terms of things like how many CPU cycles a feature uses with X player load. You seem to be talking about the design end rather than the technical end, and while certain design conventions might be argued to be superior, they are much more low level (it's good to lower the barrier to entry for the player, for example) than high-level decisions like how many classes to have. I don't see that one race is inherently better or worse than 100 races just like I don't having a single scalar representation of 'health' to be any inherently better or worse than multiple scalars representing different kinds of 'health'.
--matt
|