3 ms·
Well, I certainly agree that atleast prompting to update is worthwhile, but there are several steps afterwards -- the equivalent of installing a new application
by whichdan 14y ago
Well, I certainly agree that atleast prompting to update is worthwhile, but there are several steps afterwards -- the equivalent of installing a new application -- every time an update comes out.
- conor23 14y agoBut that is - MUST be - what you're actually doing: the equivalent of installing a new application. That is the only sane way to do it. Think of how many errors Windows' aggressive updating causes. And that is from Microsoft. They have ONE JOB! (okay, the OS division has one job). So if they do all this internal testing and still push things onto your OS that cause problems. What is a third party to do? The sane thing to do is NOT to treat is as a back door that you can push stuff over, even if the customer asks. The sane thing to do is to treat it like installing a new application. If the 'new' application has problems, then you stop making it available. You're in control. The customer is in control. It's their pc. It doesn't get broken. Really, for anything that interacts with the hardware and OS on as low a level as a display driver, there is really no alternative to massive testing beforehand. Once it's in the wild, you should not expect or have the functionality to simply push firmware or software updates. It should take work and commitment from the customer, the same as installing an application. In the case of firmware, perhaps a bit more.