i agree that the hardware needs to up to the task.  but it also seems that writing
code for windows often involves several layers of implementation, especially with
oop.

object1->do_something()  calls  generic object function which calls other functions
or winapi which calls possibly more winapi which calls code directly dealing with
hardware.  granted, i think much of this is needed to make programing better and
easier (we cant all write asm!) but it does thicken up the texture a bit,
introducing latency.  it just seems like programming used to be much more direct by
calling one function that accessed hardware.  it seems to me that directx is a way
to get around the biggest bear in win programming - the winapi.

pete