Live data from Hacker News

JQuery 1.5 Released

code.jquery.com

21–30 of 33 posts

Re: JQuery 1.5 Released

#24

I guess there’s be a blog post coming up soonish, but for me the big deal is integration of a templating language. We experimented with the MS-written templating plugin that’s now been integrated and it seems pretty good.

Beware of Microsoft's jQuery-tmpl templates, if you care about being able to render your views with reasonable performance. You can benchmark 'em yourself here: http://jsperf.com/dom-vs-innerhtml-based-templating/73 TL, Didn't Benchmark: Two orders of magnitude slower (approx) than other engines. On the iPad, for example, jQuery-tmpl was able to render a small template 181 times in a second, whereas Eco, at the other…

I don't see why its relevant how fast it can render templates: Wouldn't anything more than once or twice a second be sufficient for general needs?

Edit: I also want to point out that the linked page above is user editable, and allows remotely hosted javascript (by design). Beware :/

Re: JQuery 1.5 Released

#25

Earlier quoted context omitted.

Beware of Microsoft's jQuery-tmpl templates, if you care about being able to render your views with reasonable performance. You can benchmark 'em yourself here: http://jsperf.com/dom-vs-innerhtml-based-templating/73 TL, Didn't Benchmark: Two orders of magnitude slower (approx) than other engines. On the iPad, for example, jQuery-tmpl was able to render a small template 181 times in a second, whereas Eco, at the other…

I don't see why its relevant how fast it can render templates: Wouldn't anything more than once or twice a second be sufficient for general needs? Edit: I also want to point out that the linked page above is user editable, and allows remotely hosted javascript (by design). Beware :/

In JS web apps, the most common speed constraint you'll encounter is how fast you can render views and update the DOM. Imagine trying to render 500 list items ... say, contacts in an address book -- you don't really want that to take 3 seconds on an iPad. If it works for your needs, that's fantastic, but it's nice to be aware of the performance relative to alternatives that accomplish the same goal.

Re: JQuery 1.5 Released

#26
post #10

Very readable code, I'm sure I could learn a lot by perusing it :)

If you want to do that, I recommend starting by watching Paul Irish's "10 Things I Learned from the jQuery Source" [0] and "11 More Things I Learned from the jQuery Source" [1] as he does exactly that. There's also jQuery Deconstructed [2] to navigate the jQuery source in... an interesting manner. [0] http://paulirish.com/2010/10-things-i-learned-from-the-jquer... [1] http://paulirish.com/2011/11-more-things-i-learne…

An up-vote is supposed to be enough, but that link to the jQuery source is very cool.

Re: JQuery 1.5 Released

#28

I guess there’s be a blog post coming up soonish, but for me the big deal is integration of a templating language. We experimented with the MS-written templating plugin that’s now been integrated and it seems pretty good.

Beware of Microsoft's jQuery-tmpl templates, if you care about being able to render your views with reasonable performance. You can benchmark 'em yourself here: http://jsperf.com/dom-vs-innerhtml-based-templating/73 TL, Didn't Benchmark: Two orders of magnitude slower (approx) than other engines. On the iPad, for example, jQuery-tmpl was able to render a small template 181 times in a second, whereas Eco, at the other…

Thanks for the info. For our internal tests our app renders a template a few times a minute with ~500 nodes, but all our users are on Firefox 4 or Chrome latest so no-one’s noticed a problem. If we stard building client-facing apps I’ll definitely look at the alternatives.

Re: JQuery 1.5 Released

#29

The real question now is: When will Google APIs have this hosted on their CDN for developers to use?

If you don't mind another CDN, Microsoft seems to be hosting it: http://ajax.aspnetcdn.com/ajax/jquery/jquery-1.5.min.js (that domain is cookie-less too)

This is incorrect, Google's CDN is cookie-less too.

    $ curl -I https://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js
    HTTP/1.1 200 OK
    Content-Type: text/javascript; charset=UTF-8
    Last-Modified: Mon, 15 Nov 2010 20:40:52 GMT
    Date: Mon, 31 Jan 2011 20:03:57 GMT
    Expires: Tue, 31 Jan 2012 20:03:57 GMT
    Vary: Accept-Encoding
    X-Content-Type-Options: nosniff
    Server: sffe
    Cache-Control: public, max-age=31536000
    Age: 51530
    Transfer-Encoding: chunked

Re: JQuery 1.5 Released

#30
post #29

Earlier quoted context omitted.

If you don't mind another CDN, Microsoft seems to be hosting it: http://ajax.aspnetcdn.com/ajax/jquery/jquery-1.5.min.js (that domain is cookie-less too)

This is incorrect, Google's CDN is cookie-less too. $ curl -I https://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js HTTP/1.1 200 OK Content-Type: text/javascript; charset=UTF-8 Last-Modified: Mon, 15 Nov 2010 20:40:52 GMT Date: Mon, 31 Jan 2011 20:03:57 GMT Expires: Tue, 31 Jan 2012 20:03:57 GMT Vary: Accept-Encoding X-Content-Type-Options: nosniff Server: sffe Cache-Control: public, max-age=31536000 Age:…

You misunderstood me. You can access the Microsoft CDN from two domains: microsoft.com and aspnetcdn.com. The former has cookies, the latter does not.

From http://www.asp.net/ajaxlibrary/cdn.ashx#ajaxmicrosoftcom_ren...:

The CDN used to use the microsoft.com domain name and has been changed to use the aspnetcdn.com domain name. This change was made to increase performance because when a browser referenced the microsoft.com domain it would send any cookies from that domain across the wire with each request. By renaming to a domain name other than microsoft.com performance can be increased by as much to 25%. Note ajax.microsoft.com will continue to function but ajax.aspnetcdn.com is recommended.

Post reply on HN