To neutralize the effect of min or max borders the test is run and sampled multitude of times, then the calculated weighted mean (instead of arithmetic mean) is taken as trustworthy.
Which means, simplified, deanjo should run the tests several times and record min values each time, then do weighted mean calculation as well as provide highest min and call the end result.
I don't think it will change though. The API is on par with DX, unlike what elanthis said.
His other points - wither DX is way easier to program or OpenGL offers no multithread rendering are still not disproved.
Meanwhile microsoft has hate ++. Paying money to company (without choice mind you) that uses it to sabotage cross-platform standards and improve its own(so you have even less choice) is plain retarded. Way to go, bill & steve.
Which means, simplified, deanjo should run the tests several times and record min values each time, then do weighted mean calculation as well as provide highest min and call the end result.
I don't think it will change though. The API is on par with DX, unlike what elanthis said.
His other points - wither DX is way easier to program or OpenGL offers no multithread rendering are still not disproved.
Meanwhile microsoft has hate ++. Paying money to company (without choice mind you) that uses it to sabotage cross-platform standards and improve its own(so you have even less choice) is plain retarded. Way to go, bill & steve.
Comment