Putting Performance In Perspective

未关闭
  • 哪里不对？
#99 2 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@johnkpaul 已经在做这个了。

开始于 2012年10月16日。

评估

这个 Issue 还没有评估数据。

描述

Chapter: performance content

The internet is rife with all sorts of advice about performance, and jQuery and JavaScript performance in particular. Unfotunately, a lot of this filters down into a context-free echo chamber that has mixed-results in end-developer code. For instance, you'll see people who think nothing of nesting several AJAX calls, but then they'll end up doing a manual for loop over jQuery selections in in those nested callbacks because they "heard $.each was slow." We should breathe some sanity into this discussion and provide context for our other performance tips by explaining basic things like

  • importance of profiling
  • optimizing the things that will give you the biggest payoff/that have room for optimation (don't optimize the thing taking 1% of the time)
  • balancing performance with maintainability/readability
  • avoiding premature optimization, but also, what to prematurely optimize, e.g., caching jQuery collections is not only better because it's faster, but because it improves readability and code structure
  • library problems are likely different than your problems. in other words, if your app is slow, it's probably not because of scope chain traversal
  • if the only thing slow about your app is the overhead of $.each, have a Diet Coke
主要语言
JavaScript
星标
914
派生
472
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

jquery/learn.jquery.com 的其他 Issue

查看 jquery/learn.jquery.com 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。