|@Duoas: That's why I specified "interactive.|
I think you're replying to me, not Duoas. And yeah point taken.
|I/O isn't minimalistic in any sense:|
Yes, console I/O is extremely minimalist in every sense. It's minimalistic in that the API doesn't do much for you. All it does is input and output text. And if we're talking about standard lib API, it doesn't even give you any placement/formatting options. Very, very minimalist.
"Minimalist" doesn't mean "easier to use", in fact it's usually the opposite. Building a house with just a hammer and saw is minimalist, but is much more difficult than using power tools.
In fact that's kind of my whole point. Because the console does so little for you, you end up having to do more work -- which makes using it harder than some alternatives in many cases.
|In many cases, i/o gives you a chance to break out of the hypothetical gaming box in that you can add (without much difficulty) commands to not just "pick up the shovel" and "examine the tree" but "eat the shovel" and "shake the tree" (from Dunnet).|
Having a console interface does not give you any more options than you would have in any other interface. What you're describing could easily be accomplished with Verb buttons a la Maniac Mansion. Rather than the user typing one of several available verbs, they would click on it.
Now, I'm not saying the verb button approach is better -- I'm just saying that using the console doesn't open any additional doors for you, whereas using a window-based game lib opens several. The console just holds you back and limits what your program is capable of. Even if you want the text I/O interface, that can be accomplished with a gaming lib.