Comments on: jQuery 1.4 is released

By: DavidMark

DavidMark — Fri, 22 Jan 2010 12:39:30 +0000

Why is this rag still posting puff pieces on this dubious script? It’s beyond laughable to talk about “improvements to attr”, speed (it’s always been a tortoise) and nonsense like:-

“f you want to ensure that “this” inside a function will be permanently bound to a particular value, you can use jQuery.proxy to return a new function with that scope”

Scope?! What does – this – have to do with scope? The “experts” can’t even speak the language, so they sure as hell can’t lead neophytes anywhere but off a cliff. ;) And how is another “hitch” function supposed to be a breakthrough feature? It’s basic bullshit. And you can bet they have introduced new and exciting memory leaks with that too. ;)

And how is it that these gushing pinheads can’t seem to find the only real browser scripting news that is out there right now? They know what it is, but theyduhwanna write about it. :( Hi Dion and Ben. You have _zero_ credibility as a news source. Zip.

By: Aphrodisiac

Aphrodisiac — Fri, 22 Jan 2010 11:40:03 +0000

Excellent thanks

By: Timmyw

Timmyw — Wed, 20 Jan 2010 16:18:42 +0000

Very excited about jquery 1.4, especially the performance enhancements and per property easing.

By: csuwldcat

csuwldcat — Sun, 17 Jan 2010 02:20:20 +0000

@sixtyseconds – Yeah I saw transmorph in the forge, but still need to give props to jQuery because it was based off of their good idea.

By: rosamez

rosamez — Sat, 16 Jan 2010 21:09:52 +0000

I’m a bit sad that .require did not make it and that .proxy has no currying, but in the end I’m really really having fun with the new functions :)

By: sixtyseconds

sixtyseconds — Sat, 16 Jan 2010 20:00:29 +0000

@csuwldcat – See http://mootools.net/forge/p/fx_transmorph. You give MooTools fans a bad name with your constant, unprovoked ranting though…You should have a doctor take a look at that…

By: csuwldcat

csuwldcat — Sat, 16 Jan 2010 18:12:41 +0000

To jQuery’s credit though, the different easing per property feature is really cool!

By: csuwldcat

csuwldcat — Sat, 16 Jan 2010 17:52:49 +0000

LMFAO! jQuery must like mustard, because the really love playing katch-up… Just in case anyone hasn’t been out of their jCave in quite a while, tons of the features in this 1.4 release are features that have been in Mootools/Prototype for YEARS…here are a few that really make me say “Holy guacamole Batman, you JUST figured this out?!?”

Passing Attributes to jQuery(…) – duh, duh, and one more thing, duh.
—
Binding Multiple Event Handlers – see above, and for chr*st sake people you should ALWAYS have been able to pass in multiple props/events/attrs etc via an object in these frameworks, if you couldn’t before they screwed the pooch. Period
—
Controlling a Function’s Context – uh, this actually came from Protoype JS, regardless of this “feature” being in 1.4, you should know that jQuery calls it “.proxy()” because it has always used the now native function context modifying method “.bind()” improperly to set event handlers – so in truth, this is not a feature, it is a work-around for not keeping up to date with javascript, tear ;(
—
Delay an Animation Queue – see Mootools 1.1, circa 2006
—
Check if an Element Has Something – gee, ya think?
—
Oh, but feel free to continue with the “OMG IE7 created tabbed browsing” party…

By: DamirSecki

DamirSecki — Sat, 16 Jan 2010 17:20:51 +0000

@jhiswin:
use google load api to load jquery… and most users won’t even notice since it’ll go from their cache

By: ArianStolwijk

ArianStolwijk — Fri, 15 Jan 2010 21:39:35 +0000

@mmurph211: That was just the first thing I thought. And it does work great in MooTools.

Anyway, congrats for jQuery !

By: miraglia

miraglia — Fri, 15 Jan 2010 21:29:12 +0000

John gave a nice preview of jQuery 1.4 at Yahoo last month in the second half of this talk:

http://developer.yahoo.com/yui/theater/video.php?v=resig-testing

By: iliad

iliad — Fri, 15 Jan 2010 18:16:59 +0000

Some very interesting changes. I in particularly like the improved setter methods, as well as the focusin/out events.

By: Les

Les — Fri, 15 Jan 2010 14:51:06 +0000

>> And Joe Walker will be really excited to see that dojo.create has made it in! :)

Now jQuery needs dojo.declare().
:)

By: mmurph211

mmurph211 — Fri, 15 Jan 2010 14:16:41 +0000

Syntax example looks like Mootools

By: WillPeavy

WillPeavy — Fri, 15 Jan 2010 13:50:23 +0000

Awesome. I’m upgrading all my dev environments to 1.4 today

By: Deadmeat

Deadmeat — Fri, 15 Jan 2010 13:16:16 +0000

Ah so it’s been made default only for future PHP and Rails websites. I haven’t tested this yet. I’ve just being going from the details in the linked article.

So basically older PHP and Rails websites will still work after the upgrade, and yet they would have still worked if it was the other way around too.

So jQuery has now inherited a limitation of PHP and Rails as the default. I could understand if there was any technical merit to doing it this way. But I guess it’s just because PHP and Rails are the environments of choice for jQuery developers.

By: nhyone

nhyone — Fri, 15 Jan 2010 12:50:27 +0000

I’m also already using [] to pass arrays to PHP.

jQuery 1.4 can check if the parameter already has ‘[]‘. If so, it just does not have to emit them.

By: Deadmeat

Deadmeat — Fri, 15 Jan 2010 12:47:34 +0000

Sorry I meant:
{'param[]': [val1, val2] }
Which from what I remember is what you need to do now. It’s what AJAXing a form used in a PHP page would do now for example.

By: Menno

Menno — Fri, 15 Jan 2010 12:40:32 +0000

@Deadmeat:
{ 'param[]': val1, 'param[]': val2}
Will just evaluate to
{'param[]': val2}
so that’s not an option.

By: Deadmeat

Deadmeat — Fri, 15 Jan 2010 11:49:23 +0000

Addition to above, the new features look cool, and the performance improvements are impressive.