Comment by xmcp123
2 hours ago
It's wild to me that they don't have an Android-esque "Developer mode" that requires an obscure thing that you need to look up to see the options that can harm you (Click X times on the "Build info", etc).
2 hours ago
It's wild to me that they don't have an Android-esque "Developer mode" that requires an obscure thing that you need to look up to see the options that can harm you (Click X times on the "Build info", etc).
Historically, Microsoft never had to consider that, because Windows was always in developer mode.
The Windows pedigree assumed that everything would at most have an ini or registry setting or group policy to override 99.9% of Windows' behavior or at least an undocumented but accessible internal API to set it.
The Windows 11 transition was the first time Microsoft shipped a sufficiently bullshit OS that it actually needed a developer mode.
But most scathingly... and the original sin... was that some shit-for-brains Microsoft leader made the decision to disable configurability for purpose of boosting platform revenue.
Fuck that person, because they knew exactly what and why they were doing it, and still made that decision.
Tolerate or hate them for all their sharp business elbows, but Microsoft of yore (Gates and Ballmer eras) intentionally made the decision that if they built and owned a platform that most people used (because it worked for them) then there would be more than enough money for everyone. And that it was healthy to leave money on the table for their developers, because developers and the apps they built drove people to the platform (see "Developers, developers, developers!").
gpedit.msc