> I predict Windows will end up going this route before Google backtracks on it.
It will not happen in the next 10 years. Right now people would just make generic launchers and then use them to manually load and execute any binary they please. Options include just writing your thingy in a scripting language and run it in node.exe, python.exe, or compile it to WASM, use native bindings of a scripting language, abuse a random verified electron app, ship with and use a random vulnerably driver, etc etc.
Even remotely getting to the point where locking Windows down to that degree would be possible is going to take MS a long time, fighting friction from users all the way. The whole ecosystem would have to change drastically for that sort of control to even be possible and make sense.
The holes aren't really there because it would be so hard to close them in a vacuum, they're there because decades of software people use rely things working the old way. People aren't going to switch to a new OS on which almost nothing works anymore.
It will not happen in the next 10 years. Right now people would just make generic launchers and then use them to manually load and execute any binary they please. Options include just writing your thingy in a scripting language and run it in node.exe, python.exe, or compile it to WASM, use native bindings of a scripting language, abuse a random verified electron app, ship with and use a random vulnerably driver, etc etc.
Even remotely getting to the point where locking Windows down to that degree would be possible is going to take MS a long time, fighting friction from users all the way. The whole ecosystem would have to change drastically for that sort of control to even be possible and make sense.
The holes aren't really there because it would be so hard to close them in a vacuum, they're there because decades of software people use rely things working the old way. People aren't going to switch to a new OS on which almost nothing works anymore.