If you look at the dojo code it looks a lot like the YUI code, in that it looks like it has already went through an obfuscator.

I am sorry but I don’t know if I am going to use this library anymore I have no reason to like YUI 3.0 then I do to like dojo or jQuery. My greatest objection is that YAHOO.util.YUILoader is enforced on the user.

This was after using YUI on another project which already had it installed – in this instance it was easy to use the API to figure out what I needed to do. But installing from scratch was too difficult and I used jQuery instead.

I hope you have a basic installation example for other not-so-noobish, even a way to isntall the whole library at once to play around with it to accompany the super light install procedure.

Cheers though! Thats my only gripe.

I’m not sure I will use it. Like Marco what I want is writing JavaScript. I don’t want to learn one more syntax and one more specific usage of JavaScript. I have not the time for this. The learning curve is not so small when you want to implement things that are not only copy/paste from the examples and the docs.

Why this fucking syntax àla JQuery. Yes it’s not verbose but it’s not so easy to read and to understand when you are in maintenance phase. If I want a JQuery chaining, I will use JQuery (wich has a ton of addons), but if I have choosen YUI it’s precisely because it’s not JQuery.

I use YUI since 18 months for a huge application. With the differents releases of version 2, I sometime have to remove and replace some composants (menu, editor) because the personalisation ask to much work (changes in the CSS for example) or because the usage was not too easy and sometimes eratic (editor).
Now the team say clearly that version 3 and 2 will not be compatible. I am very disappointed because for me it’s like all this months of work could be put in trash. All must be rewrite and retested if I want to always be in the race (:-(((

I am happy to see that you took the leap and made YUI 3.x incompatible with the old stuff. While I am sure I’ll swear at you a bit while I convert stuff over, the benefits of the new interface and streamlining will definitely be worth it.

Looking forward to it!

Alan

What I always liked so much about YUI is the fact that you actually have to write JAVASCRIPT to use it. It never imposed some weird alien syntax that first needed to be learned before being able to use it like it’s the case with many other libraries.

The biggest ‘mindfuck’ is switching between 2.x and 3.0 when you have to alter use of YAHOO.util.Dom.get(‘foo’) with Element.get(‘#foo’); and other similar substantial changes. YUI 2.x is made like an uber powerful set of helpers while YUI 3 seems to want to change the way we program Javascript.

I don’t know if this makes any sense but I have some problems with calling this a 3.x version of the same library that’s currently at 2.5.2. It feels like it’s a totally DIFFERENT library and not a newer and more powerful version of a library that I already love.

I can definitely see some advantages in the new approach but I’m not sure yet whether I feel the love. Different? Definitely. Better? I’m not sure.

I suppose both approaches deserve to exist and I’m definitely not sure whether I like to see this new approach replace the 2.x one, even if this only happens in the fairly distant future.

Just my 5 cents!

Shame I just got my head round yui2, that learning curve just keeps getting higher. Hopefully not quite so much this time!

Thanks for the great effort, yui has been a lifesaver on many occasions.

Even better: the decisions you’re making are well-informed, and only help to improve an already-sound architecture. I can definitely see the performance wins that 3.0 will realize across the board.

You’re slowly but surely eliminating any reason preventing my jQuery buddies from seeing the light. ;-)