Ext3 vs. YUI3

[hello2008]

Finding hardly to see a post about the recent YUI3 (preview version).

I'm interested in the good Refactor and Architecture. It may be a strong competitor for Ext3 in the future.

Maybe it's too early to discuss version 3, but I hope Ext3 be better than YUI3 just as in the past.;)

[jay@moduscreate.com]

Hrm, didn't know about YUI3. I've been so focused on ext :0]

[alloftheabove]

I hope so too. :D

[Animal]

A look through the YUI 3 site, and it does not seem like a quantum leap from the YUI 2.* versions. Nothing like the Ext 1 to Ext 2 revolution.

[chalu]

Whatever they've done in YUI3 that tickles our fancy - we should be able (if really needed) to emulate, or isn't that allowed :-? I see it all the time - C# emulates Java then Java in turn emulates C#, then PHP comes, and attempts the enterprise by emulating Java. I think we should be able to learn from ourselves though we compete. But I would always admire Ext for it's ease of use and extension.

[harley.333]

I think YUI 3.x is beginning to show signs of code bloat. It's becoming a very powerful framework (which is good); but the features won't realistically be used on a common basis in browser apps (which is code bloat). Once web servers and web browsers support compiled JS, this will be less of an issue. And large, powerful JS frameworks might actually be in demand. But that's a few years away (in my opinion).

[fabrizim]

I have to disagree that YUI 3.x is showing signs of becoming a bloated framework.

The driving force of the new codebase is to make it more lightweight, yet increasingly powerful at the same time. The main concept, on my initial pass of the code, is that you only need to include a small js stub file. The core "yui.js" file includes a special Loader class. Then, any additional functionality is provided through modules, which are loaded dynamically, hence cutting down on any initial overhead during the pageload.

I'm not sure this type of dynamic loading is planned for the next major release of the Ext framework, but as the code is already separated into modular pieces, I think that it would be possible. It would definitely cut down on the overhead of including ext-all.js for each page load.

With all of the powerful features of YUI, and now a simple way to load only the necessary code, I think we will see a much broader user base when the 3.0 release becomes stable.

[Animal]

Yes, dynamic, incremental loading of the codebase is a decent idea, but it depends on the application.

For a single page intranet app there's not much point. Just load the code and use it.

For an internet-distributed web page there might be some point. I know jack doesn't like the idea, but I think he shoujld revisit it in the light of the YUI code loading API.