I don't agree, software needs to evolve as its dependencies does. In this case we have fetch, async/await, promises and loads more native features that jQuery hasn't adapted to (XHR is obsolete now for example).

Why include a dependency that the browser provides for free? jQuery was good before ES6/next came along, these days it's extra cruft.

And if what you're saying is true about weird corner cases, people will fix that up in PR's anyway, that's not a reason to stop innovating and just say "meh, jQuery is good enough".

Thank god most software doesn't work your way, we'd probably be stuck in the stone ages still.