Live data from Hacker News

A Conspiracy to Kill IE6

blog.chriszacharias.com

281–290 of 386 posts

Re: A Conspiracy to Kill IE6

#281

OldTuber granted you the ability to completely bypass the new Google-oriented code enforcement policies, enabling anyone holding it to commit code directly to the YouTube codebase, with only the most glancing of code reviews from anyone. No need for code readability. No need for exhaustive tests. No need for maintaining code coverage. If you broke the site by improperly wielding OldTuber status, it was on your head a…

I'm not comfortable with this. why should we need to avoid code reviews, sacrifice readibility and bypass tests to make up for poor business decision making?

Re: A Conspiracy to Kill IE6

#282
post #191

Earlier quoted context omitted.

> I don't know how they didn't all get fired. Like, ALL of em, including everyone who set up the special "OldTuber" priv long before. I can think of 2 reasons: 1. The gamble paid off. It turned out the time was ripe. Thus, there was really no negative impact on the organization that people had to be punished for. 2. The OldTubers were the experienced backbone of the group. Firing everyone with that privilege would li…

I can think of a third reason: everybody in the industry wanted IE6 dead. It was expensive to maintain support for an old, broken browser and often meant new features couldn't be added. The people who should have fired the conspirators were glad that the conspiracy succeeded even if they had objections to the methods used.

I'm really glad this method of execution was an honest banner. (The biggest problem here might've been cutting colleagues out of the loop it sounds like they were probably supposed to be in.)

When I started reading the story, I was afraid it was going to go in the direction of sneaky sabotage, like intentionally causing performance problems or crashes. There've been accusations of that happening, within the last year. Earlier, there was a long history in the computer industry of sneaky sabotage of competitors, which was suggested by the (perhaps only a joke, in that particular case) mantra "DOS isn't done, till Lotus doesn't run".

Re: A Conspiracy to Kill IE6

#283

Oh my, this is amazing. I'm not sure the engineers realized despite their secrecy, it would be noticed by the press immediately after deploy. But the best part is how Google engineers immediately on seeing it figured "oh yeah, we should do that too" (although they apparently got the necessary approvals however that was done at Google, it was easier to do because they figured "well, youtube must have done due dillegen…

> I don't know how they didn't all get fired. Like, ALL of em, including everyone who set up the special "OldTuber" priv long before. I can think of 2 reasons: 1. The gamble paid off. It turned out the time was ripe. Thus, there was really no negative impact on the organization that people had to be punished for. 2. The OldTubers were the experienced backbone of the group. Firing everyone with that privilege would li…

3. They need developers. Everyone was hiring like mad in those days, still are. They don't want to lose a big pile of good developers.

Re: A Conspiracy to Kill IE6

#284
post #39

Oh my, this is amazing. I'm not sure the engineers realized despite their secrecy, it would be noticed by the press immediately after deploy. But the best part is how Google engineers immediately on seeing it figured "oh yeah, we should do that too" (although they apparently got the necessary approvals however that was done at Google, it was easier to do because they figured "well, youtube must have done due dillegen…

It's a fascinating tech story, but it would easily turn into a horror if we weren't talking about something like a video hosting platform. Imagine working at a medical or financial company and having secretive 'old timer' permissions that basically backdoored the company's engineering processes. Even if the engineers saw a good reason to do so. I mean, who are we to say that this was doing it right ? It turned out to…

If enough developers want to do something, you can't stop them. You can make it take more developers, that is the best you can do.

Re: A Conspiracy to Kill IE6

#285
post #213

Earlier quoted context omitted.

So? It works. I'm not upgrading my Win7 box. It's a much more user-centric OS than Win10.

How so? I'm legitimately asking- I find Windows 10's Start Menu , of all things, to be way better on win10 than win7, especially in Enterprise deployments.

It's probably the forced internet login and forced OS updates and reboots that annoys people.

Re: A Conspiracy to Kill IE6

#288

Earlier quoted context omitted.

How so? I'm legitimately asking- I find Windows 10's Start Menu , of all things, to be way better on win10 than win7, especially in Enterprise deployments.

It's probably the forced internet login and forced OS updates and reboots that annoys people.

None of which are strictly _forced_ - my laptop (Windows 10 Pro) _never_ installs an update without asking me, and my mother's and grandmother's machines (Windows 10 Home) are setup without an Internet user account.

Re: A Conspiracy to Kill IE6

#289

Earlier quoted context omitted.

I call it Last Jedi'ing. GOTCHA https://youtu.be/5ECwhB21Pnk?t=323

Why do you even bring this up? What you linked isn't funny. The video is titled -- 'Why Star Wars: The Last Jedi is a Complete Cinematic Failure'. I believe I know where this is all going. Putting aside all the anti-feminist crap that I'm sure I'm going to find if keep watching this video, what I'm seeing is a very angry dude screaming 'Gotcha' while old-timey piano music is playing in the background and some starwar…

Damn you truly had a visceral reaction to this. Calm down lmao

Re: A Conspiracy to Kill IE6

#290
They should get a medal.

Microsoft was way behind in the Web era and IE6 was attempt to slow everybody else down and create web that works only with MS software.

The IE6 was prime example of the Microsoft strategy of embrace and extend using market share. They build software that included harmful features, broke standard or for no reason and had intentional inconsistencies.

Microsoft was pure "engineering evil" during the Gates era.

Post reply on HN