yui 和 yui3 的比较
YUI3准备得够成熟吗？ 与YUI相比，它有哪些优点和缺点？
Is YUI3 ready mature enough? What are its advantages and disadvantages compared to YUI?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
YUI3准备得够成熟吗？ 与YUI相比，它有哪些优点和缺点？
Is YUI3 ready mature enough? What are its advantages and disadvantages compared to YUI?
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
接受 或继续使用网站，即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论（4）
@Corwin 关于 yui.yahooapis.com 服务器上的文件更改的说法是不正确的 - 如果您使用我们服务器上的 YUI 3 PR 2 版本，即使后续版本发布，这些文件也将保留在那里。
确实，随着我们转向 beta 1（计划于 6 月）然后进入 GA，API 将会发生一些变化。 毫无疑问，我们会做出一些改变，在您升级时需要您的关注和时间。 这——以及 YUI 3 不包含 YUI 2.7.0（2.x 代码线中的当前版本）的所有功能这一事实——是现在推迟的主要原因。
您可以在此处详细了解 YUI 3 及其与 2.7.0 的不同之处：
http://video .yahoo.com/watch/3711767/10207432
我们将在下一版本的雅虎主页上使用 YUI 3。 您可以在这里阅读相关内容：
http://yuiblog.com/博客/2008/11/11/frontpage-and-yui3/
@Corwin is incorrect about files changing on the yui.yahooapis.com servers -- if you use the YUI 3 PR 2 release from our servers, those files will remain there even when subsequent releases come out.
It's true that the API will change some as we move toward beta 1 (scheduled for June) and then to GA. We will undoubtedly make changes that will require your attention and time as you upgrade. That -- and the fact that YUI 3 doesn't contain all of the functionality of YUI 2.7.0 (the current release in the 2.x codeline) -- is the primary reason to hold off right now.
You can learn more about YUI 3 and how it's different from 2.7.0 here:
http://video.yahoo.com/watch/3711767/10207432
We're using YUI 3 on the next version of Yahoo's homepage. You can read about that here:
http://yuiblog.com/blog/2008/11/11/frontpage-and-yui3/
自 PR2 发布以来我一直只使用 YUI3。 从那时起，发生了很多变化，但我的特定应用程序代码不必改变太多。 在过去的几个月里，我也一直在跟踪 YUI3 的所有主要变化。
现在是 6 月，事情似乎已经接近 beta 1，因为我看到了大量与文档相关的提交。 如果您正在寻找非常好的、功能丰富的基础 JavaScript 库，我建议您使用 YUI3 而不是 2。 如果您需要一堆通用小部件，则可以同时运行 YUI2 和 YUI3，尽管事情会很复杂并且您的代码将使用混合 API； 但你可能想坚持使用 YUI2。
YUI3 正在成为一个非常出色的库和框架，自 PR2 以来，它在功能、性能和内聚性方面已经非常成熟。
I've been using YUI3 exclusively since the PR2 release. There has been a lot that has changed since then, but my specific application code didn't have to change too much. I have also been tracking all the major changes in YUI3 during the past months.
It's now June, and things appear to be coming close to beta 1 as I'm seeing a ton of documentation related commits. I would recommend using YUI3 over 2 if you're looking for very nice, feature-rich base JavaScript library. If you need a bunch of generic widgets, it is possible to have both YUI2 and YUI3 running together, although things will be complicated and your code will be using mixed APIs; but you may want to stick with YUI2.
YUI3 is becoming a pretty great library and framework, it has matured greatly in functionality, performance, and cohesiveness since PR2.
YUI3 仍在不断变化。 如果您直接链接到雅虎服务器上的 YUI3 文件，代码库将不断变化，您现在依赖的功能或语法可能会突然改变。 YUI2 功能非常强大，如果您不想重写代码以适应不可预见的更改，那么 YUI2 将是更安全的选择。
YUI3 is still in flux. The code-base is going to keep changing and features or syntax you rely on now may change abruptly if you link directly to the YUI3 files on the yahoo servers. YUI2 is quite capable and would be the safer bet if you don't want to go rewriting your code to accommodate unforeseen changes.
我会选择 YUI3。
尽管如此，您可能会发现一些功能尚未移植到 YUI3（例如，几个月前我需要自动完成，而目前 YUI3 AC 仍处于测试阶段），在这种情况下您可以尝试这个: https://github.com/yui/2in3 它可以帮助您在使用 YUI3 时导入 YUI2 依赖项。
I'd go with YUI3.
Still, you may find some features that hasn't been ported yet to YUI3 (for example, few months ago I've needed autocomplete and, at the moment, YUI3 AC was still in beta), and in that case you may try this: https://github.com/yui/2in3 It helps you to import YUI2 dependencies while using YUI3.