Unfortunately until Windows changes, the best way for them to serve customers is to continue to inject kernel code. (This is no longer needed or even permitted with macOS.) They did screw up operationally, but one problem made the other much more likely and dangerous.

▲

baq 4 days ago | parent | next [-]

Why limit yourself to Windows? My enterprise-issued mac is very noticeably slower and suffers from weird crashes and reboot-fixes-things issues that my own personal mac has never had.

▲

otterley 4 days ago | parent [-]

Because Windows was the sole OS impacted by last year's incident.

▲

yangff 3 days ago | parent [-]

they also screwed up Linux before they did that on windows.. The problem here is they are a spyware that pushes whatever code they want to your (precisely your company) devices without test etc. It's just a matter of time for it to blow up.

	▲	otterley 3 days ago \| parent [-]
		The Linux kernel panic issue was different in many ways (in this case, the bug was in the Linux kernel used by a particular RHEL release), but your point that it needed further testing before pushing it out to production is still valid. https://christiantaillon.medium.com/no-need-to-panic-the-lin...

▲

mapontosevenths 4 days ago | parent | prev [-]

> They did screw up

The word you're looking for is negligence. The lives of human beings were at stake and they YOLO'd it all by not performing a phased rollout.