I'm not nearly as concerned with Firefox not recognizing OpenGL... there are a good number of actual English words it doesn't know.
I'm not 100% clear on this article... half the complaints are that the new OpenGL breaks compatibility with the old OpenGL, and the the other half are complaining that it's basically the same?
It sounds like they're basically waving the white flag on the API war and pretending like they were never fighting it. Which is funny, because if OpenGL was only supposed to be for CAD they should have done that about 15 years ago. I mean, how many features do CAD programs really need in the graphics department? I remember using AutoCAD back in High School about 6 years ago and (graphically mind you) it looked about exactly like the newest version of Solid works or whatever program you want to insert. Not to mention they both look like Milkshape3d... I dunno about you guys but the CNC machines i've seen only mill based on the surface mesh... which I think OpenGL had nailed down by about, what, 1992?
That's fine by me, as much as I still feel OpenGL is superior to Direct3D (go look at some DX9 vs DX10 benchmarks if you're not sure... then go look at some DX8.1 vs DX9 especially in any HL2 engine games. Then tell me why there is a 15-20% performance drop before you even start using features from the newer versions). It'll probably be for the best if Nvidia and ATI can focus on kick ass Direct3D support, which is turning into a full time job.
It's strange timing for them to give up now though, OpenGL had a HUGE opportunity to gain ground on DirectX with this whole Vista only for DX10 bullshit and they just kinda rolled over... I think a lot of developers would be excited to only write one graphic engine (rather than a DX9 engine for XP AND a dx10 engine for Vista) for their new games and still be able to run on all windows platforms AND use all the newest bells and whistles.
This comment was edited on Aug 12, 23:57.