OpenCL 2.0

If you aren't building your data-oriented, sparse voxel ray-casting + deferred rendering + real-time radiosity FUTURE ENGINE® for Tomorrow's Games™ using OpenCL™ 2.0, you're doing it wrong.

http://www.khronos.org/registry/cl/specs/opencl-2.0.pdf

>>18
No language allows you to define your own language and use it as first class constructs within the original language as well as LISP. You can use multiple languages, and if you work hard enough, you can create your own language-like abstractions, compile your language to the original lang and link everything together, but it's a lot of work. If it's a lot of work, you wont be able to do it in your time constraint. And if you wont be able to do it, you'll use some crappy hack instead. No other language can do what lisp does as well, and they pay for it. But lisp is shit for many unrelated reasons, so you couldn't use it in these environments anyways.