5 ms·

I don't mean to be so disparaging, but Microsoft really should just take IE out back and shoot it.

by brickmort 12y ago

matthewmacleod 12y ago
That's not really helpful. IE is no longer a shitty browser; why should it be killed off?
- nailer 12y ago
  It really is. Even in IE11 there's a bunch of busted basics. The CustomEvent constructor is broken out of the box. Edit: see details in post below.
  - demallien 12y ago
    I don't mean this to be a personal attack, so please don't take it that way, but comments like this read to me as being written by a young, inexperienced programmer. I happen to know that this is not your case, but without checking the username, I would immediately classify this comment as such. The people over at Microsoft are not idiots - even though Microsoft is no longer the new hotness, they still pay developers well, and have some pretty tight engineering going on. So when you say "The Event constructor is broken out of the box", my first instinct is to assume that the Microsoft engineers have implemented the constructor in their way for reasons that you're not smart enough to have grasped. But, as I said, I know that you aren't a young inexperienced programmer, so you probably have some good reasons to make the claim, which leads me to the point of this rambling post - why is the Event constructor broken in IE? I'm curious to know what specific problems you have with it.
    - nailer 12y ago
      Sorry, I didn't provide details because I probably just assume everyone here is a JS developer, which is probably a bad idea. IE11 has no CustomEvent constructor. You have to polyfill it with https://developer.mozilla.org/en/docs/Web/API/CustomEvent https://developer.mozilla.org/en/docs/Web/API/CustomEvent. Microsoft's official Twitter account @iedevchat has pointed people to the same one: note the article article says for IE10, but the issue and fix is required for IE11. It's a simple fix, but CustomEvent is ancient, and it's surprising what didn't make it into IE11.
      - deleted 12y ago
        [deleted]
        deleted 12y ago
        [deleted]
- gaius 12y ago
  When IE6 came out, it was a breath of fresh air; the fastest, most stable, most featureful, most standards-compliant browser available. It was the final piece of the puzzle that let corporate developers move away from desktop apps and onto the web wholesale. Sure it has overstayed its welcome. But I hate the revisionist attitude of some, who were still in school when all this went down.
ripdog 12y ago
Why? IE11 is a really good browser when you need something small, light, and incredibly fast. I can slap adblock and lastpass on it, too.
junto 12y ago
Any competition is good competition, no matter what the quality is. Or do you want a single monopolistic choice of Chrome to rule the world? Sorry, bit we've been there before. Embrace the variety.
- gldalmaso 12y ago
  Variety is good but Microsoft has an ugly history with standards and that is very hurtful to the ecosystem. They promised that they have changed in regards to that, but those are just words in the wind, time will tell on that. Also, they were lagging behind HTML5 standards for a long time, then they sort of caught up, now they are lagging behind on ECMAScript 6 features. Every time I check, it is Microsoft's fault that I still can't use an otherwise widely implemented feature. Quality implementation and standards adoption is the name of the game in the browser market. After 10+ years in that market, my opinion is that they have neither. The only reason they are still playing is end-user and corporate inertia.
  - pcwalton 12y ago
    > Variety is good but Microsoft has an ugly history with standards and that is very hurtful to the ecosystem. That's no longer the case. > They promised that they have changed in regards to that, but those are just words in the wind, time will tell on that. No, they aren't just words. For example, in the ES6 committee everything I've heard is that Microsoft has been doing fantastic work, right now. > Quality implementation and standards adoption is the name of the game in the browser market. After 10+ years in that market, my opinion is that they have neither. I don't think that's fair either. The implementation of canvas in IE9, for example, is a very high quality Direct2D-based GPU implementation. (D2D is still arguably the best widely-used GPU vector graphics implementation around.)

I don't mean to be so disparaging, but Microsoft really should just take IE out back and shoot it.

matthewmacleod 12y ago

That's not really helpful. IE is no longer a shitty browser; why should it be killed off?

nailer 12y ago
It really is. Even in IE11 there's a bunch of busted basics. The CustomEvent constructor is broken out of the box. Edit: see details in post below.
- demallien 12y ago
  I don't mean this to be a personal attack, so please don't take it that way, but comments like this read to me as being written by a young, inexperienced programmer. I happen to know that this is not your case, but without checking the username, I would immediately classify this comment as such. The people over at Microsoft are not idiots - even though Microsoft is no longer the new hotness, they still pay developers well, and have some pretty tight engineering going on. So when you say "The Event constructor is broken out of the box", my first instinct is to assume that the Microsoft engineers have implemented the constructor in their way for reasons that you're not smart enough to have grasped. But, as I said, I know that you aren't a young inexperienced programmer, so you probably have some good reasons to make the claim, which leads me to the point of this rambling post - why is the Event constructor broken in IE? I'm curious to know what specific problems you have with it.
  - nailer 12y ago
    Sorry, I didn't provide details because I probably just assume everyone here is a JS developer, which is probably a bad idea. IE11 has no CustomEvent constructor. You have to polyfill it with https://developer.mozilla.org/en/docs/Web/API/CustomEvent https://developer.mozilla.org/en/docs/Web/API/CustomEvent. Microsoft's official Twitter account @iedevchat has pointed people to the same one: note the article article says for IE10, but the issue and fix is required for IE11. It's a simple fix, but CustomEvent is ancient, and it's surprising what didn't make it into IE11.
    - deleted 12y ago
      [deleted]
      - deleted 12y ago
        [deleted]
gaius 12y ago
When IE6 came out, it was a breath of fresh air; the fastest, most stable, most featureful, most standards-compliant browser available. It was the final piece of the puzzle that let corporate developers move away from desktop apps and onto the web wholesale. Sure it has overstayed its welcome. But I hate the revisionist attitude of some, who were still in school when all this went down.

ripdog 12y ago

Why? IE11 is a really good browser when you need something small, light, and incredibly fast. I can slap adblock and lastpass on it, too.

junto 12y ago

Any competition is good competition, no matter what the quality is. Or do you want a single monopolistic choice of Chrome to rule the world? Sorry, bit we've been there before. Embrace the variety.

gldalmaso 12y ago
Variety is good but Microsoft has an ugly history with standards and that is very hurtful to the ecosystem. They promised that they have changed in regards to that, but those are just words in the wind, time will tell on that. Also, they were lagging behind HTML5 standards for a long time, then they sort of caught up, now they are lagging behind on ECMAScript 6 features. Every time I check, it is Microsoft's fault that I still can't use an otherwise widely implemented feature. Quality implementation and standards adoption is the name of the game in the browser market. After 10+ years in that market, my opinion is that they have neither. The only reason they are still playing is end-user and corporate inertia.
- pcwalton 12y ago
  > Variety is good but Microsoft has an ugly history with standards and that is very hurtful to the ecosystem. That's no longer the case. > They promised that they have changed in regards to that, but those are just words in the wind, time will tell on that. No, they aren't just words. For example, in the ES6 committee everything I've heard is that Microsoft has been doing fantastic work, right now. > Quality implementation and standards adoption is the name of the game in the browser market. After 10+ years in that market, my opinion is that they have neither. I don't think that's fair either. The implementation of canvas in IE9, for example, is a very high quality Direct2D-based GPU implementation. (D2D is still arguably the best widely-used GPU vector graphics implementation around.)