3 ms·
I agree with your assessment that "write once, run anywhere" will always be beholden to the lowest common denominator when it comes to games that try to push th
by kibwen 13y ago
I agree with your assessment that "write once, run anywhere" will always be beholden to the lowest common denominator when it comes to games that try to push the limits of performance. However, with regard to your statement "shared memory model in JS with concurrency primitives would be a radical change to the semantics of JS, so I don't see it happening", it isn't entirely hopeless. Intel's Rivertrail[1] and Mozilla's Parallel JS[2][3] efforts might not pan out as well as they expect, but at no point has either entity thrown up its hands and declared the situation as impossible as you imply.
[1] https://github.com/RiverTrail/RiverTrail/wiki https://github.com/RiverTrail/RiverTrail/wiki
[2] http://smallcultfollowing.com/babysteps/blog/2012/01/09/parallel-javascript/ http://smallcultfollowing.com/babysteps/blog/2012/01/09/para...
[3] http://smallcultfollowing.com/babysteps/blog/categories/pjs/ http://smallcultfollowing.com/babysteps/blog/categories/pjs/
- cromwellian 13y agoRiverTrail, like OpenCL is cool, but not every algorithm is amenable to these models.