LoseThos Graphics

I can't be in the business of having different drivers for the same class of 
device.  I must stick to common hardware.  I can't do hardware graphic card 
support for this reason.

It's easy enough to use other super-VGA or VESA modes besides 640x480x 16 color, 
but I don't have the CPU power to do it without graphic hardware acceleration.  
Just run the flight simulator, ::/LT/Demo/GameStarters/FlightSim.CPZ or the 
first-person-shooter, ::/LT/Demo/GameStarters/FPS.CPZ, to see what I mean.  If I 
struggle getting things done with the available CPU power, beginners will 
struggle more.  I want to make it easy for beginners by giving them a lot of 
slack.  That's why it will always be 640x480x 16 color.  It takes 1/37th as much 
CPU power doing 640x480x4 bit as it does doing 1600x1200x24 bit.

You may criticise my updating the whole screen at 60fps all the time, right?  
How would invalidating rectangles help the flight simulator?  It makes it worse 
and is more complicated!  Sure, I could improve the CPU load when you're at the 
command line or editing a file, but that's not when there is a problem!  If you 
cut CPU load from 25% to 10%, you've done nothing except saved some electricity 
because in both cases you have enough CPU power for the task.  If you cut from 
110% to 90%, however, you've made a noticable improvement.  Full-screen, 60fps 
video games are the second case.

Just putting a test pattern on a full-screen at 60 fps uses 15% and you need to 
do graphics calculations on top of that to get anything done.  See 
::/LT/Doc/Lectures/Graphics.CPZ.