Quote Originally Posted by Fire$torm View Post
@Slicker: Sorry, I did not mean to mislead you. My reference to a marketing ploy had to do with AMD restricting OpenCL DP functions to the high end cards in the new 6xxx series. I know very very little about programming.
Ok. Then we do agree.

The way I see it, OpenCL is to CUDA as Javascript is to Java. CUDA is pre-compiled where OpenCL is compiled per device. Or, it is like C++ vs. .NET or P-code vs. compiled code. Personally, I dislike Java because the implementations just aren't the same on all platforms even though they convince CEO's that it is and that any app written in Java should rule the world. Don't get me wrong, it has its place. It just isnt' the killer programming language that it is marketed as. Same goes for OpenCL. Good concept. Bad/impossible implementation.

If creating an OpenCL app will boost CUDA performance by automatically taking advantage of the nVidia card's features, I might give it a shot with Collatz. In fact, I have. I just get too pissed due to the inability to debug compile on demand code that it sucks when dealing with really complicated GPU code. But, it if works, it may be worth it.

On the other hand, if PG just randomly picked an obscene credit amount because they finally have a GPU app, then I'd still have to say that OpenCL sucks and I'll stick with the native apps using CUDA and CAL/Brook. I can randomly increase the Collatz credit to AQUA or PG or MW rates by simply change the steps per credit config.

Maybe we should have a 5x credit challenge on Collatz. (e.g. any credit granted during the weekend challenge pays 5 times as much as normal). I bet that would get people to participate.