News for hackers. Stuff that matters.
Re:OpenGL in 2014 by shmerl on Sunday September 21, 2014 @04:35PM (#8348194)
> Not when that "one toolkit" is worse.

Here it's the case of "worse because it wasn't made better", not because it can't be better. That's my point. So difference in approaches with this subject like between AMD and Apple shows who cares about making it better and who cares about locking developers into their platform.

Re:OpenGL in 2014 by EpicEng on Sunday September 21, 2014 @05:50PM (#8348446)
So, your "point", in everything that I have read from you thus far, is that, if the world only worked the way you think it should work, then OpenGL would reign supreme as king. We can just ignore the many ways in which it sucks because, hey, you're talking hypotheticals!

Right. Of course, the real world works nothing like the world that you have described, but ok, good luck with that.

Re:OpenGL in 2014 by eropple on Sunday September 21, 2014 @05:53PM (#8348461)
There's a lot of Linux-on-the-desktop-style wishcasting in this thread.
Re:OpenGL in 2014 by shmerl on Sunday September 21, 2014 @06:02PM (#8348491)
Or rather Apple-style lock-in cheerleading.
Re:OpenGL in 2014 by eropple on Sunday September 21, 2014 @07:21PM (#8348667)
Nobody's advocating lock-in. What is being advocated is using the right tool for the job. What has been brought up--by you--is the completely laughable notion that "abstractions don't fail" when the overwhelming majority of people involved with high-performance graphics are pretty sure that the abstractions have failed. Which is why they're going exactly the other way from your ideological wishcasting and building libraries and frameworks that are tailored to the hardware rather than using a driver to overcome the impedance mismatch at the cost of performance.

You don't know what you don't know but it isn't stopping you from talking shit. Stop.

Re:OpenGL in 2014 by shmerl on Sunday September 21, 2014 @08:02PM (#8348743)
> when the overwhelming majority of people involved with high-performance graphics are pretty sure that the abstractions have failed.

Poor abstractions. I'm not convinced that there can't be a well designed cross platform graphics API that is sufficient for the majority of cases. Prove that it's impossible or stop, because otherwise your claim that you don't advocate lock-in doesn't sound sincere.

Re:OpenGL in 2014 by EpicEng on Monday September 22, 2014 @12:10AM (#8349197)
>Prove that it's impossible.

The abominable snowman exists. Prove that it doesn't or shut up.

Re:OpenGL in 2014 by shmerl on Monday September 22, 2014 @12:25AM (#8349231)
Anything more useful to say than trolling comments? The commenter above claimed that cross platform graphics APIs aren't the way to go because they failed. I see no proof that it's not a possibility. They didn't even fail - they were quite useful in many cases but with their current downsides they didn't live up to real potential. So that can be improved by making better cross platform APIs instead of claiming that one has to run to hardware specific APIs right away and there are no other options.
Re:OpenGL in 2014 by EpicEng on Monday September 22, 2014 @12:40PM (#8351298)
I'm not trolling; I'm pointing out the fault(s) in your logic. Perhaps it is a "possibility", but it doesn't exist today, and better options are available, so why would I use an inferior implementation? Because it more closely coincides with my world view?

No, I need to get software written that runs well. Now, if my requirement is to run on N different platforms (where N > 1) then I will have to look at OpenGL. If it's not a requirement then I won't waste my time. You're comments reek of ideology and completely lack practicality. You make assumptions about a complex subject which smarter people than you or I have spent years working on and come to different conclusions.

Re:OpenGL in 2014 by shmerl on Monday September 22, 2014 @12:59PM (#8351360)
> Perhaps it is a "possibility", but it doesn't exist today

So? It's not a reason not to make one or to claim that since it "failed" everyone needs to run to platform specific APIs. That was the point.