3 ms·
To me it underlines why I find YUI3 daunting. The ui widgets they have seem elegant and certainly more comprehensive than jquery + jQUI - but the contrast in th
by amvp 17y ago
To me it underlines why I find YUI3 daunting. The ui widgets they have seem elegant and certainly more comprehensive than jquery + jQUI - but the contrast in the syntax has so far kept me from delving too deep.
But I've been working with jq long enough that it's all fairly intuitive and natural to me - perhaps a few months with YUI would give me the same level of comfort there.
Ask HN: If you actually prefer working with YUI3, tell me why?
- deleted 17y ago[deleted]
- nym 17y agoIf you're going to write large scale widgets, YUI is a better suited choice because of it's already large collection of A-grade supported widgets, and emphasis on reuse. Yahoo! has put a ton of work into making sure their widgets are accessible by the disabled. In addition, YUI3 can dynamically load resources, which can be very beneficial if you have a large collection of widgets and only want to load the code for them when it's necessary. I love both libraries, there are trade offs with each, which is why evaluating them for your project is a wise decision, if only to understand the strengths and weaknesses.
- skennedy 17y agoBuilding our application, we have moved through the various JS libraries, including JQuery, and now stick with YUI. The overwhelming reason is we need guaranteed support for all the advanced features we want to build on. JQuery is a set of element actions/seclectors, but lacks plug-ins/widgets with the core library. JQuery has active developers all over the web building plug-ins that are amazing. But if we incorporate with the plug-ins and find a bug, we have to hope the plug-in project is still active and will receive support. With YUI, we can use their supported widgets, file bugs and know we will receive attention from the YUI developers. Also, note the author's choice of code is not always the simplest and could be better written.