3 ms·

"The only reason I can think of to do this, is so that you can't have arbitrarily malevolent code running in the DLLs that mod authors write." This is the only

"The only reason I can think of to do this, is so that you can't have arbitrarily malevolent code running in the DLLs that mod authors write." This is the only reason and you go on to show that it is a reasonable thing to do given the state of the world.

yellowapple 1y ago
The other reason is that it allows these modules to be cross-platform, rather than being limited to Windows on x86-64. I doubt Microsoft cares much about other operating systems, but they do seem to care quite a bit about ARM.
- spullara 1y ago
  No native support for fat binary dlls on Windows unlike Mac is kind of lame.
- jon-wood 1y ago
  Microsoft absolutely care about other operating systems, Flight Sim runs on Xbox (which is not quite Windows), and they've started releasing games on Playstation recently as well.
naikrovek 1y ago
What I said is a solution but it is in no way the best solution.
- spullara 1y ago
  Absent fixing the vGPU problem (since Nvidia is unlikely to change their stance on this), what would be the best solution? WASM seems like a reasonable compromise to me.
  - naikrovek 1y ago
    the true fix here is to have an OS that doesn't let running code do anything it wants without at least asking for permission and then getting the OK from the user. MacOS doesn't allow that. Linux and Windows are much more what I'm talking about. That's much harder than what Microsoft is doing in this situation, so I understand (kind of) why they're doing this. Malware overall isn't going to get better, or become less of a problem; it's going to get worse. Every day that these things are delayed, the more damage is done by malware that runs before this kind of OS level security gets implemented. If this were in place, we could run DLLs all day long and if one of them decides that it needs full disk access or superuser access, you can simply not allow it when prompted. Or, Microsoft could recognize that in the context of a game that this is never ok, and simply not show you the prompt to begin with. But no, because the OS is so fucking stupid we all have to think about these things. The OS is supposed to handle this level of thing. The OS should run the applications I tell it to run, and protect me from them if they try anything stupid. The OS is supposed to sandbox applications and protect the rest of the system from any malevolence they may contain. Instead we have game teams innovating solutions like this, which are entirely unnecessary if the OS team would do their fucking jobs.

yellowapple 1y ago

The other reason is that it allows these modules to be cross-platform, rather than being limited to Windows on x86-64. I doubt Microsoft cares much about other operating systems, but they do seem to care quite a bit about ARM.

spullara 1y ago
No native support for fat binary dlls on Windows unlike Mac is kind of lame.
jon-wood 1y ago
Microsoft absolutely care about other operating systems, Flight Sim runs on Xbox (which is not quite Windows), and they've started releasing games on Playstation recently as well.

naikrovek 1y ago

What I said is a solution but it is in no way the best solution.

spullara 1y ago
Absent fixing the vGPU problem (since Nvidia is unlikely to change their stance on this), what would be the best solution? WASM seems like a reasonable compromise to me.
- naikrovek 1y ago
  the true fix here is to have an OS that doesn't let running code do anything it wants without at least asking for permission and then getting the OK from the user. MacOS doesn't allow that. Linux and Windows are much more what I'm talking about. That's much harder than what Microsoft is doing in this situation, so I understand (kind of) why they're doing this. Malware overall isn't going to get better, or become less of a problem; it's going to get worse. Every day that these things are delayed, the more damage is done by malware that runs before this kind of OS level security gets implemented. If this were in place, we could run DLLs all day long and if one of them decides that it needs full disk access or superuser access, you can simply not allow it when prompted. Or, Microsoft could recognize that in the context of a game that this is never ok, and simply not show you the prompt to begin with. But no, because the OS is so fucking stupid we all have to think about these things. The OS is supposed to handle this level of thing. The OS should run the applications I tell it to run, and protect me from them if they try anything stupid. The OS is supposed to sandbox applications and protect the rest of the system from any malevolence they may contain. Instead we have game teams innovating solutions like this, which are entirely unnecessary if the OS team would do their fucking jobs.