It's a two edged sword. MS not being strict with their OS allowed the ecosystem to flourish but also allowed malware to spread. Now their trying to tighten the screws it's making it seems a little too late.
Don't attribute to maliciousness what can be attributed to incompetence. The telemetry was probably built up with no central design as a result no easy way to turn it all off. They won't spend time fixing it till it hurts them enough.
Also the fear of telemetry being used to spy on users is overblown. More and more software products add telemetry to be able to improve how their software works. It allows them to spend time improving the features users actually use and fixing their pain points. As a result they can build better products.
Mirekusoft Install Monitor tracks where an application get installed so it can be completely removed. Disclaimer: I developed it because I was tired of applications installing wherever they wanted.
That human break reflex only happens if you're paying attention. If you fully trust the car it's possible this could happen. But again if he was somewhat attentive he should have noticed the car's lack of slowing down. I have adaptive cruise control in my car and while it's not as good as Telsa's it does get things correctly most of the time. However I don't implicitly trust it and I'm always prepared to stop.
That's exactly how most AV engines work. They stall in the kernel to do their operations. You're right the scheduler doesn't know the relationship between the AV scanning server and the user processes and it doesn't need to. The normal rules for scheduling priorities work just fine.
And regarding the kernel hooking you're talking about it's still restricted on x64 versions of Windows. Heard of patchguard. The primary reason it was needed prior to Vista was that there wasn't away to accomplish some things with the existing APIs.
It takes a while for a human to react, and think of how to respond (press brakes or swerve) to an upcoming obstable. Alot of times the human driver will swerve because they don't think they can stop in time. An autonomous car could instantly sense the obstacle and calculate the stopping distance and apply breaks.
I believe you're not accepting with that dialog just acknowledging your current settings will allow the update. Now whether there should be a way to change your settings from that dialog is a different conversation.
That's what Windows Security Center is for (reporting on AV, firewall, backups, etc.). It's better than everyone coming up with their own version of it.
I've never understood non-compete for the individual contributor. All it does is make their life harder and it probably doesn't make financial sense for the company to pursue it in court.
Administrators always have the ability to take control of a file/folder and override the security attributes no matter what the current security attributes are. And it makes sense. Think about what would happen if that weren't the case.
I agree in the past it seemed they chose backwards compatibility over innovation/changes to justify the lock-in. Now they seem to give less attention to backwards compatibility.
Slashdot Mirror
It's a two edged sword. MS not being strict with their OS allowed the ecosystem to flourish but also allowed malware to spread. Now their trying to tighten the screws it's making it seems a little too late.
I would be surprised if there wasn't a group policy setting for it.
Don't attribute to maliciousness what can be attributed to incompetence. The telemetry was probably built up with no central design as a result no easy way to turn it all off. They won't spend time fixing it till it hurts them enough.
Also the fear of telemetry being used to spy on users is overblown. More and more software products add telemetry to be able to improve how their software works. It allows them to spend time improving the features users actually use and fixing their pain points. As a result they can build better products.
Mirekusoft Install Monitor tracks where an application get installed so it can be completely removed. Disclaimer: I developed it because I was tired of applications installing wherever they wanted.
It's not only that. The ads also drain battery life so Chrome with ad-blocker is probably more energy efficient.
For Honda adaptive cruise control and lane keep assist are two separate features that are independently enabled.
Obligatory xkcd https://xkcd.com/1576/
Telsa AutoPilot 2.0
-Fixed bug where the car would crash into things if the sun was too bright
Good points but if someone is consistently braking hard or traveling too fast it points to the driver.
I'm surprised they don't have something like that already.
That human break reflex only happens if you're paying attention. If you fully trust the car it's possible this could happen. But again if he was somewhat attentive he should have noticed the car's lack of slowing down. I have adaptive cruise control in my car and while it's not as good as Telsa's it does get things correctly most of the time. However I don't implicitly trust it and I'm always prepared to stop.
Simple solution. Force the driver to keep their hands on the steering wheel. It forces them to keep some attention.
That seems to be the trend at lot of tech companies in general. Workers are no longer worth investing in. They are now disposable assets.
That's exactly how most AV engines work. They stall in the kernel to do their operations. You're right the scheduler doesn't know the relationship between the AV scanning server and the user processes and it doesn't need to. The normal rules for scheduling priorities work just fine. And regarding the kernel hooking you're talking about it's still restricted on x64 versions of Windows. Heard of patchguard. The primary reason it was needed prior to Vista was that there wasn't away to accomplish some things with the existing APIs.
It takes a while for a human to react, and think of how to respond (press brakes or swerve) to an upcoming obstable. Alot of times the human driver will swerve because they don't think they can stop in time. An autonomous car could instantly sense the obstacle and calculate the stopping distance and apply breaks.
You can actually disable Windows Update through GP so that's like forever.
They give you the phone for free and pay you $50 to watch the ads.
You can still control updates. At least for pro versions. They just made it harder. You have to change them through group policy settings.
I believe you're not accepting with that dialog just acknowledging your current settings will allow the update. Now whether there should be a way to change your settings from that dialog is a different conversation.
That's what Windows Security Center is for (reporting on AV, firewall, backups, etc.). It's better than everyone coming up with their own version of it.
I've never understood non-compete for the individual contributor. All it does is make their life harder and it probably doesn't make financial sense for the company to pursue it in court.
Of course it's still there. I am guessing OP was referring to the frequency of BSOD which has decreased as the code base gets more mature.
Alot of betas are no longer giving you a choice.
Administrators always have the ability to take control of a file/folder and override the security attributes no matter what the current security attributes are. And it makes sense. Think about what would happen if that weren't the case.
I agree in the past it seemed they chose backwards compatibility over innovation/changes to justify the lock-in. Now they seem to give less attention to backwards compatibility.