That may be true, but they are presumably already maintaining a bunch of #ifdef's for the Windows-only features.

Given the relative popularity of Windows vs Linux, it probably is worth the effort to maintain Windows-only features.

True, but Windows has the much larger market share so it becomes worth it.

> That may be true

We'll never know. That's a binary blob on your machine.

This is true, but I fail to see the relevance here. This post just comes across as a "any chance to mention Free Software" type post. This thread is talking about if this decision by Nvidia makes sense. Trying to inject "well, we could all just ignore Nvidia if you were using Free Software," doesn't really contribute much to that conversation.

> That's a binary blob on your machine.

On my machine? It's less likely than you might think.

Being able to assume the #ifdef for features go one direction can have some benefit in reasoning about the code it relates to. In other words, there may be benefits to keeping the windows features a superset of the linux features, most likely in preventing stupid programmer errors.

It goes (or at least at one time went) well beyond that. Last I heard, nvidia.o was shared across Linux, FreeBSD, Solaris, and Windows.

Don't these systems use different object-file formats?

At the very least I can confirm the object is identical (same md5sum) across Linux, FreeBSD, and Solaris. Past sources have indicated to me Windows shares his object.