First, the AMD issue isn't with the driver. It's with software included in the package. How do you not know the difference when its clearly explained in the article? The title was nothing more than click-bait for ignorant hand wavers.
Stop playing stupid semantic games. The code in question is installed alongside the driver because it's completely useless without said driver, so that makes it part of the driver package.
I actually remove drivers for devices that are no longer part of my system. Windows doesn't install them because I have automatic driver updates disabled. No because I actually monitor my system for abnormalities.
That's simply wonderful. Do you have the delusional expectation that all 500+ million Windows users world-wide do the same?
Perhaps a more rational idea might be to tell the few thousand driver developers of the world not to write dumb infinite loops that peg CPU cores, and hold them accountable when they can't even handle elementary coding practices. I was about ten years old when I discovered non-terminating infinite loops are stupid and shouldn't be done.
You only need an instalable driver to add more features beyond transport and power delivery USB has built-in.
That's exactly what we're talking about. Please do try to keep up.
iTunes won't sync the library to my iPod without said software installed. But I guess you expect the iTunes package to be uninstalled every time I don't plan having my iPod plugged in, because some incompetent programmer decided to write an infinite loop waiting for it to be plugged in.
Ya know, "to monitor my system for abnormalities". Lulz.
No because that would be stupid. Well that and disabling a device is not the same as removing it from your system, leaving the software and driver installed, and then installing another similar device to it.
You don't know what you're talking about. Disabling a device in the BIOS basically makes it not exist. That's why you get no video signal from an iGPU when you do it.
You can try to pitchfork all you want, but few on this forum accept emotional, factless arguments. Myself included. Throwing a tantrum and trying to get others on board with you is infantile and better suited for Disqus comments.
You're expending an awful lot of time defending AMD and their piss-poor driver code while blaming the user. Why is that? What exactly are you getting out of this conversation as a return on your time investment?
No programmer writes bug free code and mistakes, even boneheaded ones, slip through for any programmer at one time or another.
I never claimed otherwise. Dereferenced nullptr, outside array bounds access, thread deadlocks (etc) are all genuine mistakes and part of the job.
But an infinite loop with the only exit condition waiting for a piece of hardware being present comes under the category of incompetence, akin to using gets() for web input, or having passwords stored as plaintext.
www.techpowerup.com
Facebook
Twitter
Instagram