Retiring Internet Explorer
textslashplain.com
Retiring Internet Explorer
1–10 of 122 posts
Re: Retiring Internet Explorer
#2> I printed out the source code for the network stack and sat > down with a red pen.
Does anyone still do this to get to know new code base?
Re: Retiring Internet Explorer
#3> I printed out the source code for the network stack and sat > down with a red pen. Does anyone still do this to get to know new code base?
I've done it before, although not recently.
Re: Retiring Internet Explorer
#4> Burndown List
>> Banking, especially in Asia
My bank in China requires Windows + IE + a custom ActiveX control to use their Internet banking. As a result, I don't use it. One of my accounts can be used via their mobile app (if you read Chinese or have another phone to use camera translation). My business account cannot be, and I am therefore required to visit a branch along with my official chop (seal / stamp) whenever I want to make a transaction.
In every bank branch I've been to, the computers are using ancient versions of Windows and IE. That actually applies to the PSB (a branch of the police) too. I think it might be a while before they get off IE.
Re: Retiring Internet Explorer
#5Someone needs to tell Microsoft.
The Microsoft License Advisor, which has the pricing info for Windows,
on Firefox pops up a box which reads
"Internet Explorer Notification NaN and newer versions. Download latest version of Internet Explorer"
Re: Retiring Internet Explorer
#6The death of IE cannot happen soon enough. Our organization only supports IE11 now, but even that is still a terrible handbrake on our dev process. So many tickets get reopened because of issues found only in IE, and it limits both the features we add to our application and the general polish/look/feel we can achieve.
Re: Retiring Internet Explorer
#7> I printed out the source code for the network stack and sat > down with a red pen. Does anyone still do this to get to know new code base?
I love doing this. There is something freeing about having a physical copy of the code. For one, it is less daunting because you have a tactile sense of how much there is left to read and digest. But also, you can be more free to take notes in the margin in a way that doesn’t pollute and make the code even more arduous to read (as typing comments in the code would).
It would be great to see Github implement a printer friendly view on codebases for this purpose.
Re: Retiring Internet Explorer
#8The last great version of IE that I personally used was IE 5.1 for Mac OS 9. It was - at the time - my preferred browser on the platform and really shone brightly.
As a web designer, IE - since 6 - has been the bane of my existence. It's not nearly as bad as it used to be, but it's there.
Re: Retiring Internet Explorer
#9> I printed out the source code for the network stack and sat > down with a red pen. Does anyone still do this to get to know new code base?
I have done this once before too, with a particularly hairy multi-page function from a legacy system. Spreading all the pages over a large meeting room desk allows you to view the whole code at once, instead of being constrained by the physical size of a computer monitor. And there's something hard to describe about being able to physically manipulate the code (rearranging the sheets of paper, scribbling over the code with a pencil, etc). I hope VR one day allows for that kind of experience without wasting lots of paper.
Re: Retiring Internet Explorer
#10I had to support a really old site that another developer wrote on IE just over a year ago. Luckily I am no longer at that company. Basically 99% of development and sites worked with modern browsers but one needed site required IE6 compat mode. It would have taken months to rewrite and the company didn't want to spend resources on it. At my current job we also have a lot of IBM software that seems to work best in IE although only a few people still use it at work. Doesn't seem like IE will be retiring anytime soon.
The article (and site) from this post is very good.