 Hi, my name is Michał and I'm a member of the jQuery core team. You can find me on GitHub as M goal and on Twitter as M under score goal. I'll tell you a bit about what the jQuery team has worked on recently and what are the plans for the future. First of all jQuery is a mature library with a huge market share. If a new feature can be achieved outside of jQuery, we usually prefer not to add it to core. We're focusing on fixing bugs, improving performance and making sure the new web standards work well with jQuery APIs. From time to time we do add new features though. A few examples. CSS custom property support. You can now both set and read a CSS variable using jQuery. Array is in class manipulation. So far to handle multiple classes in jQuery, you have to pass a space delimited string. Now you can also pass an array of strings representing single classes. This aligns jQuery better with native class list API, which accepts individual classes as parameters. The same applies to remove class and toggle class APIs. Even better, with toggle class you can pass multiple classes while in the native API you can't. And the third example are even and odd methods. They are supposed to replace even and odd pseudo classes in selectors that are deprecated, but more on that later. We've recently released jQuery 3.5 which includes an important security fix. Our main focus is Adversion 4 though. This will be the smallest jQuery version for many years with many performance fixes as well. We're removing lots of deprecated APIs. Many of them can now be replaced by a native API. For example, jQuery parse JSON can be replaced by JSON parse, which is now available in all browsers. We're dropping support for many legacy browsers, most notably i9 and 10. i11 remains supported for now. jQuery has avoided browser detection for ages, opting instead for support tests. If a browser fixed a bug, the workaround was skipped automatically. An example of support tests is here. We have a container, a div, i with specific styles, and then there are various checks. We check whether a specific API returns a result that we expect. If that's true, then this variable will be set to true, otherwise it still falls. We then rely on those computed values throughout the codebase. In jQuery 4 code, most of the remaining support tests were just to detect i11 bugs. Not all, but most. i is no longer developed, bugs are not being fixed, so in this specific case, we opted to detect the browser via a document document mode check. This saves size and performance for running unneeded tests. Big changes are coming to the jQuery selector engine. jQuery 4 will no longer use Sizzle. We pulled its code to jQuery and removed lots of support tests and workruns. Sizzle supports even more browsers than jQuery ever has. This already has made some operations way quicker. Also, the way Sizzle works, if a bug is detected in how a browser handles a past selector, or if a selector uses a Sizzle-specific extension, query selector all is skipped and Sizzle does everything by itself, just as it did in browsers without query selector all support. In jQuery 4, we want to try doing everything through query selector all, rewriting a jQuery selector to an equivalent native one if modifications are needed. That query selector all-based approach means that we have to drop support for so-called positional selectors. First, last, eq, even, odd, alt, gt and nth. Most of them already had equivalent jQuery methods, even and odd were added in jQuery 3.5. And lastly, we also plan an event subsystem revactor. jQuery maintains a single native event handler per the element and type per. This allows us to dispatch events in order controlled by us, which was required to fix some old e-bugs. This is no longer an issue, but it also didn't hurt so far. To support new add event listener options, for example, to support passive events, we need multiple native event handlers though. Thanks for listening.