3 ms·

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.

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.