The Industry's Foundation for High Performance Graphics

Where the hell are my objects?

This is crap, nothing like what was promised.

For those who don't feel like digging through the spec, OpenGL 3.0 Equals:

• API support for the new texture lookup, texture format, and integer and unsigned integer capabilities of the OpenGL Shading Language 1.30 specification (GL EXT gpu shader4).
• Conditional rendering (GL NV conditional render).
• Fine control over mapping buffer subranges into client space and flushing modified data.
• Floating-point color and depth internal formats for textures and renderbuffers (GL ARB color buffer float, GL NV depth buffer float, 455 N.2. DEPRECATION MODEL 456 GL ARB texture float, GL EXT packed float, and GL EXT texture shared exponent).
• Framebuffer objects (GL EXT framebuffer object).
• Half-float (16-bit) vertex array and pixel data formats
  (GL NV half float and GL ARB half float pixel).
• Multisample stretch blit functionality (GL EXT framebuffer multisample and GL EXT framebuffer blit).
• Non-normalized integer color internal formats for textures and renderbuffers (GL EXT texture integer).
• One- and two-dimensional layered texture targets
  (GL EXT texture array).
• Packed depth/stencil internal formats for combined depth+stencil textures and renderbuffers (GL EXT packed depth stencil).
• Per-color-attachment blend enables and color writemasks
  (GL EXT draw buffers2).
• RGTC specific internal compressed formats (GL EXT texture compression rgtc).
• Single- and double-channel (R and RG) internal formats for textures and renderbuffers.
• Transform feedback (GL EXT transform feedback).
• Vertex array objects (GL APPLE vertex array object).
• sRGB framebuffer mode (GL EXT framebuffer sRGB)

Plus deprecation of older features.

This is an outrage... I am really pissed... two years of hopes so easily destroyed I only hope they stop mocking us and rename the spec to GL 2.2, as it should be...

ARB, you made a big mistake...

EDIT: ok, this was a first reaction, as I see they did change lots of stuff and I have to read the spec to understand the deprecation model and profiles and stuffs. Maybe it is all not so bad afterwards... but dropping the objects sucks

EDIT EDIT: ok, it is bad...

sorry dude, I really am

I am looking for the GL_ARB_this_is_a_f**king_joke extension promotion is their specification... can't find it...

oh, must have slept half a year: must be April 1st...

So it takes a whole year (of silence) to incorporate extensions into the core. Wow.

Well, who can blame them for keeping silent when the end result was this crap? Hell, _I_ wouldn't have said anything either...

I think the new deprecation model is a critically important move in the right direction. If the ARB will rev the API more than once over the next year to get rid of more cruft, fix selectors, and introduce a new object model, that would be a really good thing.

We are approaching the end of the road with the conventional API models now though. On at least one next generation platform, software developers will be able to write their own GL and make it as small and efficient as they like. I think this is an incredibly exciting and empowering change for graphics software developers.

I am sorry. I suspect that this is my fault.

They shot themselves in the foot by layering all that 3.0 stuff on top of 2.1. How is that going to make a driver developer's life easier?!?