Mail Archives: djgpp/1997/08/13/20:03:27
It just goes back to people thinking that in order for you to be a
great programmer you have to write everything yourself, all
utilities, libraries, everything. Damn, if you take that approach
you might as well write your own compiler. And while you're
at it, write your own operating system also. Lets see how far
you get to actually completing something. Fortunately for most
of us, in todays business world, if you take that attitude you
won't have a job for very long. That way the software engineers
that actually want to finish something, don't have to put up
with shit like that. It comes down to something very simple:
"EVOLVE, OR DIE!!!"
As I have so generously said before (who cares if you don't
want to hear it again, don't read it), we are here to write
games, games, GAMES!!!! Not, the worlds next best
graphics library. For those of you who want to do that,
great, power to you. Just don't go slamming people that
use graphics and sound libraries.
Robb Largent
John Public <jpublic AT voicenet DOT com> wrote in article
<5sr929$ehe$1 AT news2 DOT voicenet DOT com>...
> This isn't "rec.graphics.engine", or "rec.learn.to.program".
> I can't see one reason NOT to use a fitting API. It's funny that
> there's so much resistance to graphics APIs, or if not utter
> resistance, there's some unwritten rule that you have to have already
> programmed a similar API, just to prove that you could do it. But
> people kneel down and kiss the earth when they dig up a decent sound
> library. (I know I do.)
> -John
>
>
- Raw text -