Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Internet Explorer 11: “Don’t call me IE”

nczonline.net

Post reply on HN
Print view View original

91–100 of 190 posts

Re: Internet Explorer 11: “Don’t call me IE”

#91

Post by dubfan »

mmanfrin wrote: post #85
megaman821 wrote: post #78

Earlier quoted context omitted.

I have cursed at working around IE quirks more times than I can remember, but I don't dump all the blame on Microsoft. Why is this the top comment, it is just a rant/whine? What other browser released at the same time as IE6 would work well (or at all) with them modern web? Microsoft has given customers a choice on whether to update their browser or not, and by in large they haven't. Then it becomes Microsoft's fault…

Working as a developer right now, I can tell you that even IE10 has odd, noncompliant quirks. And then there's IE9 and IE8 to support as well.

Yep, a couple that I've found include no support for cursor: none (even though IE9 supports it), and a rendering bug around using gradient backgrounds on tr:hover.

Re: Internet Explorer 11: “Don’t call me IE”

#92

Post by jtms »

loup-vaillant wrote: post #43
runjake wrote: post #37

Earlier quoted context omitted.

> I still don't forgive Microsoft for being absolutely massive tools in the past. As a person who seems to defend Microsoft quite often on HN, I can't shake the feeling that if they get to first place in anything, they'll become massive tools once again. I like seeing them as the underdog, it forces Microsoft to be kinder and more free, but I think innovation and progress would be seriously hindered (once again) if t…

What does "being massive tools" mean?

in this context a "tool" is a synonym for "dick"... basically stating that Microsoft are a bunch of dicks.

Re: Internet Explorer 11: “Don’t call me IE”

#93

Post by pessimizer »

ksk wrote: post #65
TylerE wrote: post #44

Earlier quoted context omitted.

Maybe because Webkit is open source and was developed independently?

What does it being open source have anything to do with it? People didn't like it when MS did it because it introduced additional unwanted bloat in the OS that was annoying to decouple.

People had/have more than one reason for disliking it. One was that they were forcing their proprietary webbrowser product deeply into the OS for no reason other than to disadvantage any possible competition. If IE had been open, people could have competed by modifying and extending IE.

Re: Internet Explorer 11: “Don’t call me IE”

#94

Post by josteink »

t_hozumi wrote: post #69

The root of the problem is not IE specific behavior, but lack of auto-updating feature. If MS doesn't remove a barrier between versions, nothing will change.

This was already addressed in msie10 or maybe possibly earlier. Auto updates are enabled by default.

Re: Internet Explorer 11: “Don’t call me IE”

#95

Post by ygra »

josteink wrote: post #94
t_hozumi wrote: post #69

The root of the problem is not IE specific behavior, but lack of auto-updating feature. If MS doesn't remove a barrier between versions, nothing will change.

This was already addressed in msie10 or maybe possibly earlier. Auto updates are enabled by default.

I think they meant feature updates, not security updates. And those come not very frequently, but agreed, even then, they are automatic (unless some moron disabled Windows Update).

Re: Internet Explorer 11: “Don’t call me IE”

#96

Post by zaatar »

Toshio wrote: post #10

Correct me if I'm wrong. If a web developer is hell-bent on detecting ie, they could look for the presence of the activex API (like jQuery currently does in order to provide a uniform AJAX interface).

The only correct and 100% reliable way to identify IE should a web dev need to, is to look for the 'Trident' token in the UA String.

Re: Internet Explorer 11: “Don’t call me IE”

#97

Post by josteink »

ygra wrote: post #95
josteink wrote: post #94

Earlier quoted context omitted.

This was already addressed in msie10 or maybe possibly earlier. Auto updates are enabled by default.

I think they meant feature updates, not security updates. And those come not very frequently, but agreed, even then, they are automatic (unless some moron disabled Windows Update).

That was what I meant. IE now auto updates to the latest version. That means new features.

Re: Internet Explorer 11: “Don’t call me IE”

#98

Post by pohl »

loup-vaillant wrote: post #43
runjake wrote: post #37

Earlier quoted context omitted.

> I still don't forgive Microsoft for being absolutely massive tools in the past. As a person who seems to defend Microsoft quite often on HN, I can't shake the feeling that if they get to first place in anything, they'll become massive tools once again. I like seeing them as the underdog, it forces Microsoft to be kinder and more free, but I think innovation and progress would be seriously hindered (once again) if t…

What does "being massive tools" mean?

"Tool" is a synonym for "dick" that you can utter even in polite company.

Re: Internet Explorer 11: “Don’t call me IE”

#99

Post by zaatar »

bsimpson wrote: post #33

I was at CES last year, and the showing of the IE team was my favorite part of the trip. They were a bunch of younger guys who basically said "We know the guys who used to work here did some terrible things in our name. We're changing that, and we're here to tell you about it." They seemed like really cool dudes. I even went over to the mall to try a Surface when they came out. Then, I realized Windows 8 is still Win…

(Disclaimer: I worked on IE from 2007-2013)

Yes, the current IE team is extremely strong, and has only gotten smarter & stronger during the time I worked there. There's tons of meetings I've walked out of where we made a decision to do X rather than Y because "the standard says to do X" and it was the guiding principle for decision-making.

Re: Internet Explorer 11: “Don’t call me IE”

#100

Post by dubfan »

yahelc wrote: post #9
[deleted] wrote: post #2

[deleted]

Nope. IE Conditional Comments were removed in IE10. http://www.sitepoint.com/microsoft-drop-ie10-conditional-com...

They dropped conditional comments, but it still supports the @cc_on conditional compilation trick. I've had to use this to target some regressions that popped up in IE10.
Post reply on HN