I wish it also included support for XPath Query.
jQuery 4
151–160 of 313 posts
Re: jQuery 4
#152Earlier quoted context omitted.
Backwards compatibility. Apparently there are still some people stuck on IE11. It's nice that jQuery still supports those users and the products that they are still running.
This is the part that I find the strangest: > We also dropped support for other very old browsers, including Edge Legacy, iOS versions earlier than the last 3, Firefox versions earlier than the last 2 (aside from Firefox ESR), and Android Browser. Safari from iOS 16, released in 2022, is more modern in every conceivable way than MSIE 11. I'd also bet there are more people stuck with iOS 16- than those who can only us…
There are a lot of intranet web applications that require IE, and IE is still in support by Microsoft. Even on Windows 11 Edge still has IE Mode for that reason. IPhones stuck on older iOS version by definition aren’t supported by Apple anymore.
Re: jQuery 4
#153Earlier quoted context omitted.
There are some really retrograde government and bigcorps, running ten year old infrastructure. And if that is your customer-base? You do it. Plus I worked on a consumer launch site for something you might remember, and we got the late requirement for IE7 support, because that's what the executives in Japan had. No customers cared, but yeah it worked in IE7.
Oh, certainly, corporations run ten-year-old software. But for the record, IE 11 turns 13 this year [1]. Which makes it somewhat more surprising to me. [1] https://en.wikipedia.org/wiki/Internet_Explorer_11
Microsoft will support IE 11 until 2032.
Re: jQuery 4
#154Earlier quoted context omitted.
Agree if you've a library developer. If you're an app or website developer then it's your project. Everyone else should steer clear of adding to native prototypes, just so they are clean for the end user.
If you are an app or website developer, at least you won't break other's systems. But you might still break stuff in your own projects. Imagine you extend a native prototype with a method, and later the native prototype starts having a method with the same name. Newer libraries start using that new standard method. You upgrade the libraries your website depends on, or add a dependency, and this new code happens to de…
Rules beget rules.
Re: jQuery 4
#155Still one of my favourite libs on the whole planet. I will always love jQuery. It is responsible for my career in (real) companies. Live on jQuery! Go forth and multiply!
so true, 15 years of jQuery for me, it's my go to.
Re: jQuery 4
#156Related: This is a nice write-up of how to write reactive jQuery. It's presented as an alternative to jQuery spaghetti code, in the context of being in a legacy codebase where you might not have access to newer frameworks. https://css-tricks.com/reactive-jquery-for-spaghetti-fied-le...
The last major jquery app I wrote ended up using a similar reactive pattern. I had to shoehorn a custom search engine frontend into a Joomla CMS where I wasn’t allowed to change much. Good times!
Re: jQuery 4
#157jQuery is v4 now, but a lot of sites esp. wordpress still have 1.11 or 1.12 and only uses them to either doing modals(popover), show/hide(display), or ajax(fetch).
WordPress ships with 3.x and is already looking to update to 4
I was talking about a lot of sites in wordpress, not Wordpress themselves
Re: jQuery 4
#158Still one of my favourite libs on the whole planet. I will always love jQuery. It is responsible for my career in (real) companies. Live on jQuery! Go forth and multiply!
all these kids chasing the new frameworks...jQuery and .NET framework have always kept me fed!
I mean… jQuery and .NET (6+) can still feed you very well :D
Re: jQuery 4
#159Earlier quoted context omitted.
This is the part that I find the strangest: > We also dropped support for other very old browsers, including Edge Legacy, iOS versions earlier than the last 3, Firefox versions earlier than the last 2 (aside from Firefox ESR), and Android Browser. Safari from iOS 16, released in 2022, is more modern in every conceivable way than MSIE 11. I'd also bet there are more people stuck with iOS 16- than those who can only us…
It’s rarely a horrid IT department but some special or legacy software without modern replacement
But is this horrid legacy software really going to be pulling in a new major version of jQuery?
Re: jQuery 4
#160Still one of my favourite libs on the whole planet. I will always love jQuery. It is responsible for my career in (real) companies. Live on jQuery! Go forth and multiply!
Someone should just hook up a virtual dom to jQuery, it's got a whole plugin ecosystem that AI could really re-use. Jquery + Jquery UI + Jquery Plugins + AI is probably a super power we're all overlooking.