We are primarily a government contractor, and our main contract had a Siebel-based client management system (only a government would have the combination of money and stupidity to invest in an ancient technology like that, but oh well), and up until late last year, we had to run IE in the lowest security mode and IE7 compatibility mode just to make the ActiveX components function. The new version is by and large HTML5 compatible, and though they recommend Firefox, we've had only a few bumps running Chrome. I doubt more than a handful of our staff even use IE now.
A perfectly reasonable assumption, if it was in a locked room secured by armed guards. Which is really where it should have been.
Yes, well, we often hurt the ones we love.
About the only place I still see IE is on some web-based applications from the late 90s thru the mid-00s that were built using IE 5 and 6's very insecure ActiveX architecture. Up until last year, we were forced to use such software on one of our government contracts, and it literally meant viewing the site in Compatibility Mode with security settings cranked down to nothing. They finally updated the underlying Siebel engine to the HTML5 version, and after that everyone just seemed to go to Chrome. I suppose at that point where we start rolling out Win10 desktops, Edge might end up being used, but I have a feeling that MS has missed the bus here, and Chrome is king.
I think Firefox dealt it the mortal blow, and then Chrome finished the job.
Perhaps that is because it was written by SS-Oberscharführer Lennart Poettering.
So you regularly float at an altitude of 20 to 100 feet, do you?
I'd say if it's over my property at a low altitude, yes, I should have the right to shoot the thing out of the sky, and further, if I can determine who was flying it, I should have the right to sue them.
Drone operators are getting an incredible sense of entitlement out of playing with their toys. I think it's time for some serious and substantial financial penalties.
Keep your fucking toy way from my fucking property.
I was just being mischievous. I think the editors are... adequate.
No kidding. They need to be dropped on to the street from a very high altitude.
The way DICE has treated it, it's worth about whatever I can find stuck between the lint at the bottom of the pockets of my pants. Everything they've done in the last 12-24 months has only served to devalue the site.
That's all I've got to say about that.
I would disagree with this. As has been proven by high rollers on both the right and left. You're immoral billionaire's money is just as good to these 'hoes as corporate money.
Because a billionaire is just as much a product of the system than a company is. Nobody makes a billion dollars through their own work, they make it by extracting value from other people's work. Which means their wealth is a product of and dependent on the system, thus they can be trusted to be utterly loyal to the system - slaves with golden chains, but slaves nonetheless.
Kings might have had it better than peasants, but neither could opt out of feudalism. It wasn't until capitalism - a new system - began making inroads that new opportunities opened up. And now capitalism is worn at the seams, at least in the developed world, and a seemingly neverending cascade of problems defy attempts to solve them through means acceptable to the system, which has caused a predictable retreat into fundamentalism - in this case free-market fundamentalism - for many who are heavily invested in the system. Whether this is the final crisis of capitalism, or whether it can ride out the storm once again by lifting the rest of the world to the developed status remains to be seen - but either way, it won't last forever any more than any previous system has.
My proposed solution is simply that they don't force updates on those who don't want them, and instead allow users to defer or completely ignore unwanted updates and only install software they want on their own computer. This solution looks remarkably like how previous versions of Windows have worked prior to the new policy.
I'm seeing conflicting messages about what you can and can't defer/block now. For example, some posters in this thread have said you could already block driver updates before, but other sources (including the article you linked to) imply that this was not previously the case and has now been changed in response to the Nvidia driver problems that triggered this discussion. In any case, this is all academic if they do the sensible thing and don't force any update on any unwilling recipient.
Certainly some of these companies do have decent customer support -- I don't mean to imply that such issues never get resolved.
The trouble is, unless they all have good support, there is a risk involved in having automatic updates that wasn't there before.
What I honestly don't understand after all the discussions here and elsewhere in recent days is why so many people seem to be defending Microsoft's position. If they're worried about security issues not being patched, they could just as well leave updates on by default but optional, so those who know what they're doing can take steps to apply the important patches with proper testing and without risking unwanted side effects, while those who just plug in and go will probably get exactly the same result as they would with compulsory updates anyway.
As far as I can see, there is literally no reason not to do this -- which is basically status quo for most systems today -- unless someone at Microsoft has intentions that mean they would want to push an update that a clued up user/sysadmin would not want to install, which is the only time it makes a significant difference whether or not the updates are mandatory.
In such cases it is paramount that you contact the hardware vendor and insist that they provide an updated driver to ensure that it works in your environment.
But seriously, the reality is that you have no power whatsoever to compel an organisation the size of say Nvidia or AMD to provide working drivers. Both provide drivers for their gaming cards that are frequently buggy as hell. Even their much more expensive professional workstation cards -- where almost the entire point is the supposedly better drivers, because the hardware is all but identical -- have all kinds of silly driver bugs that have been known to cause anything from screen glitches while using supposedly certified applications to outright system crashes.
Several people have commented in this Slashdot discussion that you can disable the driver updates within Windows update even if you can't disable other parts, though so far I haven't been able to find any official confirmation of that from a Microsoft source. Even if it's true, that in itself says something about Microsoft's awareness of the potential for forced updates to go badly wrong.