Last time I used windows in a big corpo settings, there were so many things pudding off both us Devs but also IT.
Switch out a bad RAM stick? Spend an hour with IT.
Use a software? Spend an hour (or days) with IT
Compile your own software? Believe it or not, spend large amounts of time with IT
Like the compiler on a windows PC can’t work without different windows protection systems gets in the way, repeatedly. And then your executable, or some .d’ll just get wiped off the disk 😐🤷🏼♀️
I don’t think they do it intentionally, but big corpos don’t give a shit about their workers conditions, so if they were to enforce things (with backdoors ofc, so that if needed you can deactivate things, remember the unique installation code for windows like 95 or 98?) the grunts will just have to eat it up. And they would probably not have a much harder time, everything is already locked down hardware wise so they are used to all that jazz.
FreedomAdvocate@lemmy.net.au 2 weeks ago
None of your examples at the start I’d that comment make sense or are true.
Also you’re talking about corporate policies for businesses that use windows, not windows itself. Management of devices is one of the biggest reasons why windows is the only real option for big corporations.
Valmond@lemmy.world 2 weeks ago
Oh I’m very absolutely talking about windows itself, it’s the reason you have go through so many loops to do the tiniest thing.
My point: Microsoft is already doing what you’re supposing they never will.
BTW your first phrase doesn’t make any sense?
FreedomAdvocate@lemmy.net.au 2 weeks ago
Yeah sorry just fixed the autocorrect/complete in first sentence.
Where and how are Microsoft doing this? Where are they removing the ability to “sideload” programs unless the developer is registered with Microsoft?