Disclaimer: I work for microsoft, but nowhere related to the phone team.
Edit: My point is more about interfaces than design. I know nothing about typography.
Also, textual interfaces usually make it easy to say, "now group that set of operations and give it a convenient name" (scripting), while graphically interfaces usually don't, and users are stuck with whatever individual actions the UI designers added to menus.
Neither tendency is inherent in using text or graphics, but it usually works out that way. I've wondered about this for a while, but text vs. graphic interface discussions ("keyboard vs. mouse", which often overlap) usually miss that distinction, much like they do "approachable to new users" vs. "efficient for committed long-term users".
That's actually one of the things that worries me about Windows Phone 7's UI - it's very heavily text-based, which facilitates first-time usage (no getting things wrong there, unless your text really sucks), but punishes expert/frequent users.
Text takes up a disproportionate amount of screen real estate compared to, say, iconography. They are also harder to scan, their location harder to keep consistent (due to document flow), and given that most people's memories are visual first and linguistic second, harder to remember and make an impression upon.
On small devices, loading your page up with text is generally a bad idea. Obviously unavoidable in certain circumstances (say: reading an article), but there are a lot of things out there in the design world that isn't typography.