1. 5
  1.  

  2. 2

    the Fetch API can replace jQuery’s Ajax functions

    Except that it won’t work for 7% of your visitors, which I consider to be a pretty significant number (imagine a store turning away 7% of its customer base!)

    1. 2

      You’d probably just polyfill it, then? It’s easy to do. I wouldn’t consider it a blocker for ditching jQuery :)

      1. 1

        You’d probably just polyfill it, then

        Isn’t that essentially what jQuery is? Besides, jQuery does more than just Ajax (and if you don’t use that part you can make a custom build without ajax).

        It’s easy to do

        I’m not so sure about that, because it’s not just the fetch API you need to worry about. If you look at Bootstrap’s efforts to remove jQuery then they had to do a lot of work and write helpers to ensure cross-browser compatibility. Turns out not everyone is running the latest Chrome.

    2. 1

      New frameworks […] make it easy to break up a UI into components. They are designed to handle rendering a page as well as updating it. jQuery is typically only used for updating a page, relying on the server to provide the initial page. React, Angular, and Vue components, on the other hand, allow for a tight coupling between HTML, code, and even CSS.

      Yes, few developers (and, it seems, even fewer designers) have ever truly valued progressive enhancement. It only was, for a time, the least inconvenient way of doing things. Once designs started calling for orders of magnitude more complexity, developers turned against the inconvenience with approaches that throw progressive enhancement out the window; with such approaches available, they are now filtering down to everything. So progressive enhancement now requires a choice to actively inconvenience oneself, and as a result, we are finding out that progressive enhancement never actually was a widely-held value. It merely happened to be the default, for a time, by a happy accident of history.