21–30 of 175 posts
But as users, creators of highly customized workstations and rabid fans of particular development environments, doesn't it bother anybody but me, that the browser choice has been hijacked?
Sure, its just stupid Windows users, they don't care. Is that it?
Every IE UI is different, and they seem to be spiralling down is usability. I'm particular about optimizing my own time and changing UI to suit Microsoft's agenda is definitely going to piss me off.
Earlier quoted context omitted.
IE8 is the max for XP so until XP goes away it will be the new IE6, which is at 1% in the US. So, yes IE8 will have another decade.
Is IE8 really that bad with regards to standards ? That's an honest question.
Earlier quoted context omitted.
IE8 is the max for XP so until XP goes away it will be the new IE6, which is at 1% in the US. So, yes IE8 will have another decade.
Is IE8 really that bad with regards to standards ? That's an honest question.
But it is a huge step up from IE6 so if a large chunk of those people suddenly find themselves at IE8 then the world will be better for it.
I wish MS would go back and try to update the IE8 render engine so that it can use some of the newer standards of IE9 or even IE10.
I'm not a fan, and I don't understand the gushing. As developers, I suppose folks are glad to reduce their support matrix? But as users, creators of highly customized workstations and rabid fans of particular development environments, doesn't it bother anybody but me, that the browser choice has been hijacked? Sure, its just stupid Windows users, they don't care. Is that it? Every IE UI is different, and they seem to…
Old browser versions have been a detriment to web development for years. This is definitely a step in the right direction.
And here I thought that all non-updated IE versions were installed in environments where Sysadmins blocked the updates (and will in the future). It would be interesting to see a number of how many installations this change could really target. Like, how many IE 6 to 8 are actually in the wild. Can't be that much, imho.
There's something about this that really bothers me, maybe someone can better clarify.
Why are admins enforcing a policy that leaves the company target to just about every possible security hole that has been fixed in the past 20 years?
Is there a valid reason for this that I'm unaware of?
The article points out that MS will still provide blocking tools for companies. Corporations are the major source of IE6 browsers and I'm not sure this will have any impact on them. The best we can hope for is that high consumer adoption rates will force many more sites to drop IE6 support which might spur companies to finally test and upgrade.
Furthermore, apparently "future versions of IE will provide an option in the product for consumers to opt out of automatic upgrading". Source: http://windowsteamblog.com/ie/b/ie/archive/2011/12/15/ie-to-...
I'm not a fan, and I don't understand the gushing. As developers, I suppose folks are glad to reduce their support matrix? But as users, creators of highly customized workstations and rabid fans of particular development environments, doesn't it bother anybody but me, that the browser choice has been hijacked? Sure, its just stupid Windows users, they don't care. Is that it? Every IE UI is different, and they seem to…
Chrome follows the same model, which is what I use, and I prefer it. So, I think it's a good idea, and not because Windows users are "stupid."