Comment by CamouflagedKiwi
7 days ago
It's also kind of pointless. Almost immediately, something will be installed that will require installing the .NET runtime, maybe multiple versions of it.
If the argument is to try to prohibit it, then it just won't work as a platform, because too much existing software won't work on it. There's a lot of garbage I'd love to not have (all the stupid hardware config apps all the manufacturers push on you) but just having that functionality not work can't be the answer.
> all the stupid hardware config apps
Similar pet peeve, and I think the solution to this is the platform setting, adopting, and enforcing conventions. Something like what has happened with notebook trackpads[1] about a decade ago, and more recently RGB peripherals[2]—no more cancerous giant Electron app to move a few sliders and set an RGB hex code.
[1]: https://learn.microsoft.com/en-gb/windows/win32/input-precis...
[2]: https://learn.microsoft.com/en-gb/xbox/gdk/docs/features/com...
> no more cancerous giant Electron app to move a few sliders and set an RGB hex code
That will also ship vulnerable drivers.
>Almost immediately, something will be installed that will require installing the .NET runtime, maybe multiple versions of it.
That's because Windows ships with an ancient .NET 4.8.1 by default. Purely a mistake on Microsoft's part not to bundle modern .NET with their product and force software packaging hell.
Sure, that's only made worse by the suggestion here to not install any version of it at all.