151–160 of 167 posts
Am I the only one who finds all the happy faces Microsoft have injected into the page a bit weird? It feels like they are trying to sell me some bad news but make me feel happy at the same time. Don't get me wrong - I think it's a good move to discontinue support for older IE versions... There is just something with all the smiling and laughing faces all over the page that make all my alarms go off
everyone smiling there is a frontend dev
My definition of a modern browser is one that self-updates, this is essential for security. There are plenty to choose from, but if you're using a browser that doesn't keep itself up to date you're asking for security problems.
Earlier quoted context omitted.
The latest IE for Vista SP2 looks to be IE9, so it looks like it'll continue to receive updates. https://support.microsoft.com/en-us/lifecycle#gp/Microsoft-I...
Sigh I blame Microsoft's confusing description: > What is end of support? Beginning January 12, 2016, only the most current version of Internet Explorer available for a supported operating system will receive technical supports and security updates. Internet Explorer 11 is the last version of Internet Explorer, and will continue to receive security updates, compatibility fixes, and technical support on Windows 7, Win…
Given Vista's reputation, I'm willing to bet Microsoft doesn't feel a need to address the few Enterprises who are stuck on Vista SP2 until its support ends.
I'm curious if anyone knows a company that plans to ride out Vista SP2 until its support ends. Seems like most companies did the XP to 7 hop (and are currently hoping to ride 7 until it sunsets).
It's pretty interesting to see Microsoft edging out onto this limb of abandoning their long held policy of supporting their software for long periods of time. There is pretty much no alternative, so on the one hand it is not like their enterprise customers have anywhere else to go. On the other hand, it's one less argument for companies to stick with Microsoft if they are already on the edge. I'll be interested to se…
The amazing thing is that Microsoft took this long to correct what should have been an obvious mistake: that IE versions apply like other Windows components and they should only need to support the most up to date one for that OS version.
The kind thing here is that Microsoft has taken ownership of that mistake, publicly admitted that they made it and that the fix was coming, and given companies more than a year and a half (and advertising to that effect, such as the site linked here) to adjust to the fix.
Are there any guesses when the support for IE 11 ends? Or when will Microsoft remove IE from Windows? Never?
IE 11 ends with Windows 10. Edge the Browser isn't classified as a Windows component, to my knowledge, and so also shouldn't classify for "extended support" like IE has in the past. It certainly sounds like the intention is to drop IE entirely once Edge has feature parity and user adoption on its side.
(Things are a bit trickier when talking about EdgeHTML the Renderer which I would think is a Windows component still, given that it runs some of the Windows Universal Platform, but here also the benefit of forking it from IE is that they can keep the support policies clear from day one as opposed to having to fix up things after the fact like they did here.)
The document makes things wildly unclear as to which versions of IE are actually supported by Microsoft. In practical terms it's still IE9 and IE11 for a while (so far as I can tell)? https://support.microsoft.com/en-us/lifecycle#gp/Microsoft-I... I'm sure there is still a load of Windows Vista SP2 machines around...
My thoughts too. If versions of Windows less than Windows 7 are supported which cannot run IE11, and IE11 is the only version being supported, are those older versions of Windows still really supported? Windows Vista has support through 2017 and Windows Server 2008 has support through 2020.
https://support.microsoft.com/en-us/gp/microsoft-internet-ex... provides a clearer overview of what the supported version where is. (Note that it excludes OSes that are currently supported by end support before 12 Jan 2016.)
Earlier quoted context omitted.
It made some sense at the time the law was conceived. SSL was crippled to uselessness by US export restrictions. IE 6 had a monopoly. So they built their own much more secure encryption (using ActiveX to plug into IE) and mandated its use for everything that matters. The incompetence was in mandating a certain implementation instead of writing a technology-neutral law requiring a certain security level.
Interesting! So bad actions by the US gov led to bad results for US companies....
There are a lot of businesses that use older versions of Windows and use Internet Explorer as their default web browser and use group policy from a Windows Server to prevent the install of a third part web browser. Forcing everyone to use IE. They will be vulnerable to attacks because of this and they will refuse to pay money to upgrade from XP or Vista to go to Windows 10. It will be because their business software…
In many cases we are talking about organizations using software that requires not just an obsolete internet explorer version, but an ancient one. There have been many years to assess and fix this problem, and just because companies stuck their heads in the sand and expected it would always be someone else's problem. I have little pity for the companies, but I feel deeply for the IT employees that will have to deal wi…
Management required that I use VBScript and ActiveX controls, but I had to use JavaScript in cases when VBScript was too slow. Each new version of Internet Explorer would break compatibility and require a rewrite. For example using and programming for IE 4 would break when IE 5 came out and even the AcitveX controls would not load properly. We had to switch from some ActiveX controls Kodak made to use Lead Tools instead to load TIF images of the employee pictures. Then IE 6 came out and broke that and required a new version of Lead Tools and other stuff.
There were people with Macs, OS/2, and Linux that could not use the ASP made websites because they couldn't run ActiveX and VBScript. So I suggested to management that we replace the ActiveX objects with Java objects and use JavaScript instead of VBScript and we could then make it so that the Non-Windows systems could access the Intranet web apps. Management hated that idea and ordered me to never use Java because it wasn't made by Microsoft and they didn't understand it.
But yeah each new IE version broke compatibility in the way management wanted me to develop web apps. I can see why companies want to stay with an older IE version and older Windows, because of the time and money it takes to upgrade the websites to the newer IE versions.
Earlier quoted context omitted.
> Buying or developing technologies that rely on weird proprietary quirks of free versions of software isn't very sane. There's not even a business model in place you can rely on to continue to want to support you since it's free. It's all very well saying this now, but I wouldn't be surprised if at the time these technologies were seen as JavaScript is now. I remember Adobe Air was when it came out...
Javascript has a standard (or more accurately, current javascript is the implementation of a version of the standard). It's a much safer bet that either there will be backwards compatible implementations later or that you will have other options. To my knowlesde, IE's feature set was always "what's supported by the current release". It's sort of like having a codebase which you can't change which makes use of a bunch…
I had open sourced this script to detect the OS and web browser so that it would run JavaScript code using if statements for each platform to solve compatibility problems. It should still work today but the ActiveX detection is broken because of the way JavaScript changed.
http://www.javascriptsource.com/repository/javascripts/2005/...