He realized they didn't need to replace the fixed-function pipeline. They needed to subsume it. The old way would become just one special, pre-written program among infinite possibilities.
That simple loop replaced hundreds of lines of glBegin / glEnd with a flexible, GPU-accelerated pipeline. opengl 20
did not arrive with fireworks. In 2004, many developers clung to the fixed-function pipeline because shaders were intimidating. But within two years, every major game engine had converted. Within five years, fixed-function was dead in mobile and desktop graphics alike. He realized they didn't need to replace the
Mark Kilgard, a principal engineer at NVIDIA and a knight of the OpenGL Architectural Review Board (ARB), stared at the glowing runes on his monitor. For a decade, the OpenGL way had been pure: glBegin() , glVertex() , glEnd() . A state machine of immutable laws. You told the hardware the light was a point source, the material was shiny bronze, and the transformation was a perspective projection. The hardware obeyed, predictably, beautifully. But it was rigid. That simple loop replaced hundreds of lines of
, allowing developers to write custom vertex and fragment shaders for more realistic lighting and special effects. Rendering Capabilities : Introduced Multiple Render Targets (MRT)
This feature let developers ask the GPU: “How many pixels would actually be drawn if I rendered this object?” If an object was completely blocked (occluded) by another, you could skip rendering it entirely. This accelerated complex 3D scenes with dense geometry.