The developers at the time talk about why the secretly 'IE 6 Assassination Plan' was successful



The Internet Explorer , published in 2001, was used for a long time until the end of support in 2014, but in the later years, many people said that it should ' kill quickly ' due to security issues and bugs. It was rising. Chris Zacharias, who worked as an engineer on YouTube, is also one of IE6's supporters, and at that time, he recalled that the 'deep assassination plan' was standing up by sleepless development members.

A Conspiracy To Kill IE6

According to Zacharias, at that time, under certain circumstances, the effect of HTML attribute selectors that IE 6 does not support could trigger crashes or blue screens. In addition, IE6 reads “/” of the root path as a src attribute in the blank, and the img tag suddenly behaves like an iframe tag, so the engineer in charge removes the img tag whose src attribute is blank. It was said that it was a browser that took a lot of effort, like being overwhelmed. Although IE6 causing problems immediately was a source of concern for the development team, it continued to struggle because it was ordered that 'Do not stop supporting IE6' in 2009, when IE6's share was still 18% It is said that the situation that I had to do was continuing.

At that time, development members who only slept for 2-3 hours each day sat down in the cafeteria of YouTube and discussed, an idea came to light. Members who lost their kindness to the user due to lack of sleep and thought that 'If you can not finish support publicly, what if you threaten the user to stop support?' The threatened user may stop viewing YouTube or send a threatening email to development members, but it is believed that he may start to advocate 'use a better browser'. I mean. And the team thought out this 'fancy' as 'the actual plan'.


Christiaan Colen

This plan is very simple, and it says 'We will not support your browser. Please upgrade to a newer browser' on top of the movie being played in the browser using IE6 It is something to be displayed. And next to the message, I made a link to a browser such as Google Chrome, Firefox, IE8, Opera. The message could be closed by the user at will, dare not show a clear deadline, and was presented as vaguely as possible so that the development team would not have to plan for the 'deprecation plan for IE6 support'. The code is said to have been made unrivaled to keep the eye on YouTube surveillance. The developers thought that no one would notice the banner, as no one on YouTube had already used IE 6 except for members of the web development team.

Google's acquisition of YouTube was completed in 2006, but later, when integrating YouTube with Google, engineers who originally worked for YouTube had a special authority called 'OldTuber'. OldTuber can commit Google-directed 'google-oriented' code directly to YouTube's code base, eliminating the need for code readability, thorough testing, code coverage, etc., plus reviews It was supposed that anyone would go. However, if you use OldTubeer improperly and break the website, you risk losing the authority of OldTuber or, in the worst case, becoming fired.

Mrs. Zacharias's bosses, together with the early members, were out of the IE6 assassination plan, but throughout the work some staff had the powers of OldTuber. As these members were not YouTube's early members, Zacharias said that the situation at that time was 'the situation where the owner of Ferrari had accidentally handed over the passers-by as passers-by'. Zacharias and others are using OldTuber's powers to actually embed the code on the website, as no one was honestly the key to returning the key to the assassination plan.

A few days later, a PR team leader who was informed of the presence of a banner on an inquiry from a news site visited the web development desk in a striking manner. But fortunately, the content of the news media favors YouTube's spec changes: 'YouTube is responsible for creating a faster, safer web for all users' and 'The Internet is profitable' The response was such that the web development team talked about the situation and persuaded the need to expand the coverage of the web media. On the other hand, it turned out that no one in the PR team was using IE6 as expected, so the PR staff could not confirm what was happening. It is said that the PR team has said that 'do not do anything like this again without notifying them' and headed for web media response so as not to miss the occasion like this one.

Next came lawyers in panic state. The point of the lawyers was 'Why did you let Google Chrome appear first?' Lawyers were concerned that the European regulators were intriguing anti-competitive behavior, and argued that the banner was not acceptable. However, the team did not give priority to Chrome, and the order changed every time the browser was updated, so the lawyers pulled out when they demonstrated it.

Zacharias, who was thinking that “the next ones will be engineering managers. It would be very angry,” but on the day when things came to light, the managers did not visit Zacharias. did. On the next day, some of the engineers who read the article came to celebrate the implementation of the banner ad, but asking the boss there was no fact that the angry managers had punished the boss. So, when Zacharias asked the manager in reverse, 'I thought that I copied the banner of Google Docs,' and the unexpected answer was returned. Confused Zacharias opened Google Docs in IE6, and a banner appeared, just like Zacharias and others displayed on YouTube.

In fact, the Google Docs development team wanted to stop supporting IE6 for a long time, but, like members of the YouTube web development team, their bosses didn't give them permission to stop support. The Google Docs development team immediately noticed that the banner appeared on YouTube's movie, and convinced his boss to show YouTube's banner as evidence that 'You should do the same if you need it.' Then make and implement the same banner when OK comes out. At that time, the Google Docs development team was supposed to misunderstand the YouTube banner as 'a legitimate process'.


Ultimately, the engineering management team visits the YouTube web development team, and after being questioned by their superiors, it is clear how the banner implementation decisions were made and the fact that the results justified the means Yes. At that time YouTube, Google Docs, as well as some Google services are displaying a banner for IE6, and Google has permission to put banners for other services. After a few months, IE6 users will halve their users, and IE6 traffic will drop by more than 10% across the Internet. Meanwhile, the use of other browsers has increased. In other words, the results are much better than the original web development team had anticipated.

Zacharias seems to be putting a soccer ball button in the movie, with the sound of vuvuzela resounding, while saying that 'I will never implement the code again and again.'

BZZZZZZ: YouTube Gets A Vuvuzela Button (Seriously) | TechCrunch

in Software, Posted by darkhorse_log