Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

JQuery 2.0 Released

blog.jquery.com

Post reply on HN
Print view View original

31–40 of 226 posts

Re: JQuery 2.0 Released

#31

Post by apendleton »

dmethvin wrote: post #20
apendleton wrote: post #4

The addition of the ability to just use querySelectorAll as the selector engine and not ship Sizzle is a pretty big deal, and not something I remember being included in earlier discussions about jQuery 2. qSA still includes a pretty broad set of selectors, and the ability to get the build down to 10k minified and gzipped puts it squarely in Zepto's territory, size-wise, eliminating the need for that particular wheel…

If you use really simple class and id selectors, the qSA-based selector engine may be fine. However, I think a lot of devs would be surprised about how much Sizzle is doing for them.

qSA does a lot more than class and id selectors; those have been trivial since long before qSA came along. You can also do selection on element attributes, parent-child selections (include strict child selection with ">"), and a few other higher-order selector combinations.

Still, I don't mean to slight Sizzle, and certainly won't stop using it. It's just nice to see jQuery compete with Zepto, since apparently there's a demand for a build that small, and jQuery is better-tested and less brittle.

Re: JQuery 2.0 Released

#32

Post by ancarda »

felixthehat wrote: post #10

I wish Microsoft would shoehorn at least IE9 into XP, maybe like Chrome Frame. It's crazy how many people are still stuck with XP/IE8 which is a massive web dev headache.

I'm annoyed XP doesn't have IE 9 or DirectX 10+, but I guess that's Microsoft's way of getting people to upgrade to newer versions of Windows.

Based on current stats, I'd say IE 8 hasn't got long till you can ignore it but it really depends on how much market share you care about. Do people STILL target IE 6? IE 8 is on ~10%[1] and at the current rate it's dropping at should be at 5% by October - Just in time for IE 11?

As for blaming XP, I'm not sure you can completely. IE 8 is the default browser of Windows 7 and XP has more than double the market share of IE 6/7/8 combined. Most IE users seem to be schools and companies that haven't upgraded. Although IE 6 will definitely be gone by April 2014, we could very well be stuck with IE 8 for a very long time.

For the record, IE 6 and 7 should be ignored completely. Combined they have a market share of less than 1%.

For a rule of thumb, I commonly drop support once a browser crosses 5%. Might seem high but usually once it's at that level, it's only going to keep falling.

Something to look forward to, my estimates[2] put Firefox 3.6, Safari 5/5.1 and IE 6/7/9 to all be gone by the start of 2014. Of course, linear estimations should always be taken with a grain of salt.

[1] http://gs.statcounter.com/#browser_version_partially_combine...

[2] http://cl.ly/image/2d1G3Y1Q2m3k

Re: JQuery 2.0 Released

#33

Post by KaoruAoiShiho »

apendleton wrote: post #4

The addition of the ability to just use querySelectorAll as the selector engine and not ship Sizzle is a pretty big deal, and not something I remember being included in earlier discussions about jQuery 2. qSA still includes a pretty broad set of selectors, and the ability to get the build down to 10k minified and gzipped puts it squarely in Zepto's territory, size-wise, eliminating the need for that particular wheel…

Is there a list of features of what sizzle does over qSA

Re: JQuery 2.0 Released

#34

Post by ahoge »

oneeyedpigeon wrote: post #16

I cannot believe IE8 is now considered 'old'. It is the second most used browser+version on our site, and has about 80% as much usage as the leader, IE9. Can't see IE8 support being droppable for many years yet.

Even IE9 is pretty old. It's over 2 years old by now. IE8 is over 4 years old.

IE11 will be released soon. How many versions of IE do you intend to support?

Re: JQuery 2.0 Released

#35

Post by chollida1 »

spicyj wrote: post #15
JoeCortopassi wrote: post #13

I think what a lot of people are upset about here, is jQuery entered the web development scene as "the library that solved cross-browser compatibility issues". Now while IE 6 is an obvious one to drop, IE 7 is a little tougher, and IE 8 is down right impossible to drop at this time. I understand that jQuery wants to promote a modern framework, but people didn't adopt it for it's fancy features. They adopted it becaus…

I don't think that's true. There were a handful of competing libraries (Prototype.js, Mootools, etc) and jQuery won out because people seemed to prefer its API.

Only one data point here, but we originally chose jquery for browser compatibility support and I know we're not alone:)

The rest of jquery was just gravy.

Re: JQuery 2.0 Released

#36

Post by dmethvin »

apendleton wrote: post #31
dmethvin wrote: post #20

Earlier quoted context omitted.

If you use really simple class and id selectors, the qSA-based selector engine may be fine. However, I think a lot of devs would be surprised about how much Sizzle is doing for them.

qSA does a lot more than class and id selectors; those have been trivial since long before qSA came along. You can also do selection on element attributes, parent-child selections (include strict child selection with ">"), and a few other higher-order selector combinations. Still, I don't mean to slight Sizzle, and certainly won't stop using it. It's just nice to see jQuery compete with Zepto, since apparently there'…

I didn't mean to say that's _all_ you can do, but people often expect more than qSA can deliver, especially if they've been using jQuery/Sizzle for a while. Sizzle also works around bugs in qSA implementations when they exist.

qSA's design shortcomings have been well documented, John Resig did a blog long ago about them [1].

The list of what you lose if you remove Sizzle is in the native selector file [2].

[1] http://ejohn.org/blog/thoughts-on-queryselectorall/ [2] https://github.com/jquery/jquery/blob/master/src/selector-na...

Re: JQuery 2.0 Released

#37

Post by dmethvin »

KaoruAoiShiho wrote: post #33
apendleton wrote: post #4

The addition of the ability to just use querySelectorAll as the selector engine and not ship Sizzle is a pretty big deal, and not something I remember being included in earlier discussions about jQuery 2. qSA still includes a pretty broad set of selectors, and the ability to get the build down to 10k minified and gzipped puts it squarely in Zepto's territory, size-wise, eliminating the need for that particular wheel…

Is there a list of features of what sizzle does over qSA

Posted elsewhere, but https://github.com/jquery/jquery/blob/master/src/selector-na...

Re: JQuery 2.0 Released

#38

Post by [deleted] »

KaoruAoiShiho wrote: post #33
apendleton wrote: post #4

The addition of the ability to just use querySelectorAll as the selector engine and not ship Sizzle is a pretty big deal, and not something I remember being included in earlier discussions about jQuery 2. qSA still includes a pretty broad set of selectors, and the ability to get the build down to 10k minified and gzipped puts it squarely in Zepto's territory, size-wise, eliminating the need for that particular wheel…

Is there a list of features of what sizzle does over qSA

[deleted]

Re: JQuery 2.0 Released

#39

Post by yuhong »

ancarda wrote: post #32
felixthehat wrote: post #10

I wish Microsoft would shoehorn at least IE9 into XP, maybe like Chrome Frame. It's crazy how many people are still stuck with XP/IE8 which is a massive web dev headache.

I'm annoyed XP doesn't have IE 9 or DirectX 10+, but I guess that's Microsoft's way of getting people to upgrade to newer versions of Windows. Based on current stats, I'd say IE 8 hasn't got long till you can ignore it but it really depends on how much market share you care about. Do people STILL target IE 6? IE 8 is on ~10%[1] and at the current rate it's dropping at should be at 5% by October - Just in time for IE…

AFAIK DX10+, D2D, DWrite etc was designed for the new driver model introduced with Vista and if XP display drivers are used they either don't work or fallback to software rendering. And yes IE9+ depends on D20/DWrite for its rendering, particularly for canvas etc.

Re: JQuery 2.0 Released

#40

Post by jhack »

philh wrote: post #24
dmethvin wrote: post #19

Earlier quoted context omitted.

Sorry if I seem cranky, but did you READ the blog post? jQuery 1.9 supports those browsers and the jQuery team still supports it. Do you have a problem with us supporting a second version that can be smaller, faster, and work in places other than obsolete browsers?

It looks to me like he's worried (or saying that other people are/might be worried) about how long 1.9 will continue to be supported for.

From the post: "...we’ve got jQuery 1.x to handle older browsers and fully expect to support it for several more years."
Post reply on HN