Opengl 20 -

These issues would eventually lead to OpenGL 3.0 and later the radical deprecation of OpenGL 3.1. But in 2004, developers were just happy to have shaders.

If you want to dive deeper, let me know: opengl 20

While efficient for the standard rendering of the 1990s, this approach was creatively stifling. If a developer wanted an effect that the hardware designers hadn't anticipated—such as realistic water ripples, cartoon-style cel shading, or advanced shadow mapping—they were often out of luck. They had to rely on clever tricks or proprietary extensions, such as NVIDIA’s "Cg" or various assembly-language shader extensions, which were often vendor-specific and difficult to manage across different hardware. The industry was evolving, and the rigid fixed-function pipeline was becoming a bottleneck for visual innovation. These issues would eventually lead to OpenGL 3

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. If a developer wanted an effect that the