|In that context I was referring to DOS. And the Console is just the evolution from DOS.|
Err... the concept of a command prompt (aka: "the console" or "the terminal") predates DOS. It's been around since computers had keyboards.
DOS was an operating system (or rather a family of operating systems) which used a terminal as its primary means of user input. But it wasn't (and isn't) the only one -- nor was it even the first.
I know at least Unix was around before it (by about 10 years), but I'm sure there were others as well.
|There was a time where the DOS API was limited and good games were still created. Before Doom, etc. which is the 90s not the early 80s. |
DOS wasn't really a multitasking OS. Nor did it maintain exclusive control over hardware like modern OS's do. Programs written for DOS could (and often did) communicate directly with hardware via register accesses, rather than using an API provided by DOS.
Because of that, games (even in the early days of DOS) were never really limited by any API. Though, obviously those days are long gone. And hardware communication in user-level programs is now abstracted away for various reasons.
But really... none of this has anything to do with the original topic... which I can only assume was about the console and not about DOS at all. If you really are talking about DOS (which I suspect you aren't -- you must still be getting the two confused)... then you're absolutely insane to suggest he should write DOS games.
|Maybe I should specify; I do not count newer rogue RPGs that use graphics as rogue game.|
Then you're kidding yourself. They play exactly the same except they have graphics. That's like refusing to call modern Final Fantasy's RPGs because they're in 3D, and "real RPGs were 2D!"
Welcome to the future. Oh wait... not the future... I mean... 14 years ago. Yeah, welcome to 14 years ago.
|most of these text based games give good practice on creating interesting algorithms|
You learn all the same lessons from making an actual game. Except you're also making an actual game in the process. And therefore it's much more fun and it keeps you much more engaged, so you learn the lesson faster.
|Its not a waste of time, because it makes no difference what LIB or Language you use when you wish to increase your skills at creating better algorithms.|
He wants to make games. So why would you recommend anything other
than a library that makes games? It doesn't make any sense.
If someone comes to you saying the want to learn to play the violin, do you tell them to learn how to play the cello first? Of course not. It's a wasted step.
Learn to do what you want to do. Don't waste time on intermediate steps that don't really do anything for you.
|Its almost like people seem to think that programming is just in the languages|
I fail to see what that has to do with anything.