I hate to burst everyone's bubble but if the developer originally took advantage of multi-threading, correctly, then switching to this should make no difference.
It's actually kind of bad, in my opinion, that it made such a huge impact on his application.
I was going to start going off on what a boob you are for essentially calling the developer too dumb to code however you think is "correct"... but, in a way, you are showing EXACTLY why Apple developed this tech in the first place : To make it easy for developers of all kinds to make their apps as efficient as possible, without much effort.
How could the developer have originally offloaded CPU cycles to the GPU by "taking advantage of multithreading correctly"? That's what OpenCL provides.
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
I hate to burst everyone's bubble but if the developer originally took advantage of multi-threading, correctly, then switching to this should make no difference.
It's actually kind of bad, in my opinion, that it made such a huge impact on his application.
I was going to start going off on what a boob you are for essentially calling the developer too dumb to code however you think is "correct"... but, in a way, you are showing EXACTLY why Apple developed this tech in the first place : To make it easy for developers of all kinds to make their apps as efficient as possible, without much effort.
You still suck though.
How could the developer have originally offloaded CPU cycles to the GPU by "taking advantage of multithreading correctly"? That's what OpenCL provides.
@Spencer, my comment was referring to grand center dispatch. Naturally you'd use other techniques to use the GPU.
It was multi threaded already.