News for hackers. Stuff that matters.
Re:If you were involved in the OpenGL ES specification, you ... by saurik on Tuesday June 19, 2012 @10:27PM (#4135343)
Right, but again: those are the parts of the API that are already discouraged and downright deprecated as of OpenGL 2.0. If you were developing an app targeting OpenGL 2.0, following what I understand are the best practices for that version of the specification, OpenGL ES will require little to no porting.

The problem then, arguably, is not that OpenGL ES is called OpenGL but that OpenGL 2.0 added an entirely unrelated pipeline to that used in OpenGL 1.3: you could then claim "how dare they reuse the name for what is now two APIs stuck into one library". However, they shared a lot of underlying conventions, and they were honest about bumping the major version number.

If anything, the fact that jwz is happy he proved--that you can build an OpenGL 1.3 emulation library over OpenGL ES--would argue to me to /not/ include the 1.x features as part of the standard, but to instead encourage third parties to distribute such libraries. The fixed function pipeline wasn't removed from the API as it is unimplementable, but because it is a ton of obsolete code that 2.x coders avoid anyway.

Re:If you were involved in the OpenGL ES specification, you ... by bigiain on Tuesday June 19, 2012 @11:45PM (#4135528)
" … but to instead encourage third parties to distribute such libraries."

What _I_ took away from jwz's rant (and agree with), is that if providing backwards compatibility to existing users is something one guy can do in three days (including doing the research to find out exactly what's getting taken out of an API), then it seems entirely reasonable to expect a "well behaved" standard like OpenGL to have provided the 1.3 emulation library themselves. Second best would be have a well defined deprecation period with appropriate warnings to developers, which they also failed to do according to jwz, or did properly in OpenGL 2.0 according to you. Whichever of you is right there doesn't _really_ matter much, since it's arguing over whether they got the "second best" thing right, when they seem to have failed at the "right" thing.

Re:If you were involved in the OpenGL ES specification, you ... by greggman on Wednesday June 20, 2012 @12:01AM (#4135558)
It's not something that can be done in 3 days. Fixed function on top of shaders is a PITA. If you want any kind of speed you've got to generate shaders on the fly based on which features you've turned on or off. Otherwise you create an uber shaders that's show as shit.

glBegin, glEnd are shit APIs given how GPUs work now-a-days.

Worse, things like flat shading require generating new geometry on the fly.

Fixed function pipelines suck balls.

OpenGL ES 2.0 FTW!

Re:If you were involved in the OpenGL ES specification, you ... by johnl87 on Wednesday June 20, 2012 @02:06AM (#4135815)
Finally someone actually works in the cg industry replies. +1 to this. No one really uses fixed function stuff these days, everything is shaders and vertex and index buffers. There are no fixed function hardware units, everything in the graphics pipeline is programmable and done in shaders. Even using fixed function stuff on today's hardware forces the driver to compile a built in shader. In the interest of keeping driver size small (for mobile apps), they force the programmers to write their own shaders and throw away the fixed function stuff that would bloat the driver and slow the shader compiler.
Re:If you were involved in the OpenGL ES specification, you ... by c3d on Wednesday June 20, 2012 @02:26AM (#4135854)
New code doesn't use fixed function stuff these days. JWZ's point is that there is more than new code. Legacy code also matters, e.g. CAD applications. Those have little use for shaders. Frankly, your point of view sounds very game-centric to me.

Both nVidia and ATI have committed to supporting these older APIs for the foreseeable future.

Re:If you were involved in the OpenGL ES specification, you ... by seclorum on Wednesday June 20, 2012 @05:49AM (#4136281)
Old code doesn't just convert itself to using shaders and vertex and index buffers.

Also: old code isn't necessary un-useful code.

Re:If you were involved in the OpenGL ES specification, you ... by alttab on Wednesday June 20, 2012 @10:36AM (#4137160)
Maybe not - but imagine the loss in hardware sales and ecosystem revenue if everyone ported old shitty games without re-writing them, causing batteries to die quickly and a poor user experience?

It was for the better of the industry. Boo-hoo. If it took him 3 days then hes a smart fucker. As someone with plenty of OpenGL AND OpenGL ES experience, I'd say it would have taken him just has much time to port his existing code.

Re:If you were involved in the OpenGL ES specification, you ... by CountSessine on Thursday June 21, 2012 @03:11AM (#4140887)
And if that were the end of the story, I think we'd be able to call it a day. But everyone has this funny expectation that that old code should keep getting faster with newer GPUs, in spite of the fact that GPUs don't work the way those programs were designed to use them.

Getting modern GPU performance, or anything close to it, through the crufty old immediate-mode API code is like drawing blood from a stone. Eventually developers need to take some responsibility for the code they're maintaining and migrate to a more modern API. Even on the desktop they'll have to do this - when their customers ask for modern GPU features, they'll have to move to OpenGL 3, which doesn't have immediate-mode either.

Re:If you were involved in the OpenGL ES specification, you ... by gioele on Wednesday June 20, 2012 @10:46AM (#4137211)
> If you want any kind of speed you've got to generate shaders on the fly based on which features you've turned on or off. Otherwise you create an uber shaders that's show as shit.

I think jwz's point is that he prefers having his old code run very slow through a compatibility layer rather than having to port the same not-so-important old code over the new APIs.

He wants to trade developer time for execution time, something that may be very sensible in some cases (probably not in most, but for fancy screensavers...).

Re:If you were involved in the OpenGL ES specification, you ... by w0utert on Wednesday June 20, 2012 @11:50AM (#4137517)
> I think jwz's point is that he prefers having his old code run very slow through a compatibility layer rather than having to port the same not-so-important old code over the new APIs.

If that's what you want, just write it yourself once (which he did) or use one of the many (subsets of) fixed-function pipelines running on OpenGL ES that others have made. The official 'Programming OpenGL ES 2.0' book even shows you how to do most of it, with example code included.

What jwz fails to recognize is that OpenGL ES does not only have to run on iPads, iPhones or other relatively high-powered mobile devices, but also on extremely low-powered devices with really small memory sizes (RAM and ROM) where every byte (code or data) counts. Compared to mobile devices at the time the first OpenGL ES API's were designed, an iPad could almost be considered a supercomputer. For OpenGL ES, small API size was one of the design constraints, simple as that.

Last but not least, OpenGL ES was supposed to become the industry standard for mobile 3D graphics, which means it needed strong industry support. Stuffing the API with loads of crap that almost nobody would use would drive up implementation costs for no good reason. Programmable shaders are called 'programmable' for a reason, if you want to do very specific stuff with them (such as emulating the fixed-function OpenGL pipeline), there is nothing preventing you to do so.

The single point I can kind of agree with is that maybe they should not have used 'OpenGL' in the name of the API, because it suggest at least some form of compatibility with previous OpenGL versions. Confusing indeed, but not really worth the kind of rant in this article.

Re:If you were involved in the OpenGL ES specification, you ... by fpgeek on Tuesday June 19, 2012 @11:07PM (#4135438)
OpenGL 2.0 was released in September 2004 (Wikipedia).

OpenGL ES 1.1 (which jwz complains about here) was ratified and publicly released in August 2004 (going back to OpenGL ES 1.0 would only make the comparison worse, of course): http://www.khronos.org/news/press/khronos-group-announces-th...

That's a quite, um, impressive deprecation cycle, I suppose.

Re:If you were involved in the OpenGL ES specification, you ... by prodigal_erik on Wednesday June 20, 2012 @12:55AM (#4135687)
Seven years is not a long time. My toaster is older than that, and I like to think the people who made that would be embarrassed if those cheap moving parts had decayed so quickly.

You probably have enough horsepower at your disposal to emulate each and every computer you ever bought (simultaneously!) and run all that software forever. But instead we're going to require any tool you want to use to be rewritten half a dozen times over the course of your career alone. And why? Because fuck you, we just can't be bothered to start taking engineering seriously.

Re:If you were involved in the OpenGL ES specification, you ... by msbarnett on Wednesday June 20, 2012 @02:33AM (#4135867)
If bread had changed as much as GPUs have in the past seven years, your toaster would be obsolete, too.

This isn't about good engineering vs bad, this is about mature technology vs a rapidly developing field. Different characteristics beget different engineering trade offs.

Re:If you were involved in the OpenGL ES specification, you ... by gaius on Wednesday June 20, 2012 @06:17AM (#4136355)
Cars are switching from petrol to hybrid to electric motors, but roads still work... "Rapidly developing" is a red herring.
Re:If you were involved in the OpenGL ES specification, you ... by Jtsummers on Wednesday June 20, 2012 @09:35AM (#4136868)
Bad analogy.

Car engines and transmissions are the heart of the vehicle, and those change frequently as well. Roads are a fundamental, static, landscape feature today. They're like telephone poles and fiber conduits, neither of which have changed much in recent times.

Software APIs change to match the features/needs of the users and developers. Part of this is based on the changing hardware, part on desired features. The hardware today is vastly different than when OpenGL 1.1/1.5 was available so why should we be constrained to use it in the same fashion?

In short, APIs shouldn't be static for now and forever, we'd only be limiting ourselves and ignoring the fact that sometimes things change and sometimes early decisions were wrong (or less effective than desired).

Re:If you were involved in the OpenGL ES specification, you ... by tinco on Wednesday June 20, 2012 @07:18AM (#4136466)
Roads still work because they are too expensive to replace. GPU's and bread are not, so your argument does not make sense.
Re:If you were involved in the OpenGL ES specification, you ... by gaius on Wednesday June 20, 2012 @07:44AM (#4136519)
Expensive things are more likely to work? I can tell you've not worked long in this industry, my friend.
Re:If you were involved in the OpenGL ES specification, you ... by Symmetry on Wednesday June 20, 2012 @09:54AM (#4136943)
I think that paraphrase was slightly closer to the opposite of what tinco said than what he did say.
Re:If you were involved in the OpenGL ES specification, you ... by batista on Wednesday June 20, 2012 @08:05AM (#4136562)
>Cars are switching from petrol to hybrid to electric motors, but roads still work...

Yes, and this is what makes this a bad analogy.

Re:If you were involved in the OpenGL ES specification, you ... by geoffpado on Wednesday June 20, 2012 @03:37PM (#4138736)
He's got the whole analogy inverted. If roads were rapidly changing, we'd need dramatically different cars to handle the new roads.
Re:If you were involved in the OpenGL ES specification, you ... by saurik on Tuesday June 19, 2012 @11:18PM (#4135459)
Touché: I apparently wanted "OpenGL 1.5", not 2.0. This, in fact, undermines part of my argument regarding the major version number. Further, reading through the history and timeline a bit better, I am now concerned I was horribly misinformed. I would just ignore my comment.