Hacker News Reader

Comment by pjc50 | Hacker News Reader

If even one game does this, the IHVs and OSVs will freak out, remove pre-compiled binaries from future drivers, and never let us have them again, and you’ll be the one responsible for ruining all the fun. You don’t think they’ll be able to remove it after you ship it? There are ways...

Future of computing right here.

View on HN

Most importantly, the whole point of having a driver do compilation for you is compatibility. AMD's GCN, for example, currently has three different generations out, and there are small differences in the set of supported instructions and in the instruction encoding.

Not having to deal with legacy stuff in instruction decode is one of the big advantages GPUs have over CPUs, and it relies on having the driver do the compilation.

All that said, it's nice that people are having fun with AMD's and Intel's GPU ISA, but honestly, why on Earth do they do it on Windows? There are perfectly fine open source drivers available on Linux that you can easily modify to play around with the ISAs as much as you wish.

In my experience, the vast majority of realtime rendering engineers work on Windows (because of the products). The landscape is starting to change, but I'd spitball still 99% Windows ownership. Even for console development, the platform is Windows

Because, like it or not, Windows is the platform for graphics programming.

- Debugging tools available

- SDKs for game consoles

- Advanced CAD/CAM (not everything is on UNIX)

- Platform of choice for PC demoscene

Convenient for the normal case, yes, but I was highlighting the "don't do this lest you invoke the wrath of the platform gods who ban your code" aspect of it.

(Yes, this (presumably) doesn't apply if you're using the open source drivers on Linux and accepting whatever tradeoffs apply there.)

Reply on news.ycombinator.com