5 Comments

  1. Matija
    · Reply

    Would it be possible to move IE support to a separate plugin like legacy jQuery?

    Report

    • Sally G
      · Reply

      That is an interesting idea; most folks would get the benefit of the higher speed, new features, etc., while those who for whatever reason must stay with IE 11 would not be totally shut out.
      I am definitely not knowledgeable enough to comment on the practicality, but I like the thought process.

      Report

    • Dan Walmsley
      · Reply

      It probably wouldn’t be practical. Some language features can’t be polyfilled, and the effort required to maintain such a plugin would quickly outstrip demand for it.

      IE11 is only going to become less prevalent and more broken over time – even Microsoft is actively discouraging anyone from using it, pushing everyone onto Edge. Even if a compatibility effort can be justified now, how much justification will it have in 12 months when IE11 usage is 1/10th of what it is today?

      Report

  2. Sally G
    · Reply

    Removing support for a browser should be very carefully considered and with lots and lots of notice to users. The next shiny thing that the old browser cannot accommodate may not be something that most users care about, though developers always want to be cutting-edge.
    I am concerned about the users who are required to use a particular browser more than those who have free choice. I would like to hear more about the reasons—corporate culture can be changed, technical ability of devices perhaps not so easily, does governmental regulation or censorship come into play at all?
    From a sustainability perspective, smaller files mean quicker speeds and less energy—until the next iteration of features clogs everything again.

    Report

    • Dan Walmsley
      · Reply

      You should try using the web with IE11. It’s already very broken because Facebook, Twitter, Google and almost everyone else out there already dropped support, and nobody tests their stuff in IE11 anymore. Claiming to support IE11 falsely encourages IE11 users to believe that everything will work in that browser – it won’t.

      For example, Jetpack has a feature called Publicize which automatically publishes posts to social networks. The whole flow works great in all browsers… except IE11, because facebook.com/twitter.com just show an error page. Same with share buttons.

      Report

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: