Comments on: YUI 3 Is Out!

By: CaliPhilli

CaliPhilli — Thu, 08 Oct 2009 06:27:10 +0000

Good starting point:
http://blog.davglass.com/files/yui/combo/

By: Sembiance

Sembiance — Tue, 06 Oct 2009 17:14:52 +0000

@tercero12:

“1) You have a public website. You have everything to gain and nothing to lose by linking to Yahoo’s CDN.”

I disagree with this statement slightly. While I certainly see and understand the advantage of linking to Yahoo’s CDN, there is something you lose.
If Yahoo’s site is slow or down, your site is now slow or down too.
Does that happen very rarely? Oh sure, but it does happen.

Also, if you concatenate and minify YUI along with your site javascript too and serve it up in a single script file from your server, you save yourself an HTTP request out to the YUI CDN.

By: tercero12

tercero12 — Fri, 02 Oct 2009 03:23:50 +0000

@carstepHUN & V1: Yes it does use Yahoo’s CDN in order to speed up downloads and increase the chance of cache hits. If you want to serve it all from your own server, then you have the option of disabling the combine feature such that each piece is requested individually or you can write your server-side combiner (comeon…how hard is it to write a program that reads a list of files and bundles them all together).

But consider the scenarios:
1) You have a public website. You have everything to gain and nothing to lose by linking to Yahoo’s CDN.
2) You have an intranet site. You’re most likely on a high-bandwidth connection so you’re not going to be hurt by 30 http requests over a pipelined connection.
3) You have a private (SSL-enabled) internet-facing website. This is the one case where building your own combiner makes sense. Again, if building a combiner is difficult for you, you should consider another profession.

By: V1

V1 — Thu, 01 Oct 2009 21:29:28 +0000

@carstepHUN

I think by default it uses the Yahoo CDN. Which also combines the files on the fly for you.

By: CarstepHUN

CarstepHUN — Thu, 01 Oct 2009 13:50:31 +0000

@shadedecho
that means, I need to use some server side technology to provide such behaviour of js framework, or I totally missed something, anyway I’ll look at the documentation and see how it’s implemented

By: shadedecho

shadedecho — Thu, 01 Oct 2009 13:32:37 +0000

@carstepHUN
From what I understand, YUI takes care of figuring out which modules to request based on what you declare you need, and then it still transfers them in a single HTTP response. The point is, if you need less, you get less. But if you are declaring dependencies for most of the YUI suite, you’ll get all of them (probably/hopefully) all at once, which will be similar to YUI2 experience. But if you need less, things should be snappier.

By: Willywongi

Willywongi — Thu, 01 Oct 2009 12:20:16 +0000

@someguynameddylan I agree about the oddity of using colon in ids, but it’s totally legal (w3c speaking) and I found it useful to build some sort of logical hierarchy in (#tree, #tree::node, #tree::node::leaf) that can’t be achieved through the DOM.

By: CarstepHUN

CarstepHUN — Thu, 01 Oct 2009 11:31:34 +0000

I would say, that splitting YUI into smaller parts is against the rule to have less http request for a page based on Yahoo’s advice imho.

By: grayrest

grayrest — Wed, 30 Sep 2009 23:41:55 +0000

One thing that’s not mentioned in this blurb is that the YUI team sliced most of the modules into very small pieces so the code footprint for importing (say) a single widget is WAY smaller than it is for the YUI2 equivalent. The event system and the flow/control thereof is also much improved so overriding specific behavior is easier.

FWIW, I’ve been poking at it for a few months now and it’s the first library since MochiKit that I’ve been impressed with for client side app building (I only like jquery for adding ajax sprinkles to a server side webapp).

P.S. Last I heard Dojo’s Acme was faster than Sizzle.

By: Jadet

Jadet — Wed, 30 Sep 2009 19:04:43 +0000

Wrapping everything you do with functions that load dependancies looks horrible, I get the idea behind it but would’ve liked it if that was taken care of internally.

By: someguynameddylan

someguynameddylan — Wed, 30 Sep 2009 18:38:38 +0000

I really wish they would have used Sizzle. That engine hauls. However I will reserve judgement if I could see some updates to Slickspeed and Taskspeed using YUI 3. @Willywongi I know edgecases should be accounted for, buy why a colon in your element id?

By: jdlfkandslkfajs

jdlfkandslkfajs — Wed, 30 Sep 2009 18:11:29 +0000

Yahoo says:

YUI().use("node", function(Y) {
   Y.one("#message").setContent("Hello, World!");
});

Javascript says: document.getElementById('#message').innerHTML = 'Hello, World!';

By: Willywongi

Willywongi — Wed, 30 Sep 2009 14:53:26 +0000

@Alexleonard: this is nothing but a finished project. Many modules are still in beta, and (@roosteronacid) Sizzle has some major points over YUIs selector: for instance, you will not want to use dots or colons in ids, the selector can’t handle them (see http://yuilibrary.com/projects/yui3/ticket/2528057)

By: alexleonard

alexleonard — Wed, 30 Sep 2009 13:48:21 +0000

I’m a little sad to see that CSS Grids has been dropped from YUI3 – I was really looking forward to an updated implementation of that.

I know they do plan on bringing it back with a fancy new approach, but it’s a shame it couldn’t make it into the GA of YUI3..

By: stoimen

stoimen — Wed, 30 Sep 2009 12:29:01 +0000

Just great!

By: roosteronacid

roosteronacid — Wed, 30 Sep 2009 11:42:27 +0000

Question is: Did the folks at Yahoo! throw out their own selector-engine and implement Sizzle? And if they did, why are they keeping it a secret? :)