From: Brian Osman <osmanb AT rpi DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: directx? for djgpp (sort of :)
Date: Wed, 19 Feb 1997 13:51:59 -0500
Organization: Rensselaer Polytechnic Institute, Troy NY, USA
Lines: 32
Message-ID: <330B4BCF.4DA0@rpi.edu>
References: <19A218A3372 AT csd DOT inp DOT nsk DOT su> <5ef2b5$k3e AT flex DOT uunet DOT pipex DOT com>
Reply-To: osmanb AT rpi DOT edu
NNTP-Posting-Host: darkwing.stu.rpi.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

nikki wrote:
> 
> it's what all the winblows fanatics like to stick their tongues out at the
> dos users for and claim that they have hardware acceleration, therefore
> winblows should rule the world or something ;) it's supposed to give an
> interface to all video cards so they can be treated alike (which is no bad
> thing of course)
> 
> regards,
> nik
> 
> --

I'm not a windows weenie, so don't flame me, but Windows does offer more
than
just video card support. By abstracting the video, sound, input (mouse
and
keyboard) subsystems, programmers are insulated from all of those
aspects.
Remember when games were written that REQUIRED you to have a Creative
Labs
Soundblaster? Hmmm, there monopoly sure went the the way of the hula
hoop.
Windows did it. I own an Ensoniq Soundscape now, and no one in the
world,
except the guys at Ensoniq that write the layer between my card and the
DirectX/Windows sound system need to know a thing about that card. Sure,
windows has drawbacks, but it's really hard to claim this is one of
them. It's
probably the biggest benefit.

Brian