Putting Performance In Perspective
@johnkpaul ya está trabajando en esto.
Desde el 16/10/2012.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
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
- Lenguaje dominante
- JavaScript
- Estrellas
- 914
- Forks
- 472
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de jquery/learn.jquery.com
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
jquery/learn.jquery.com#828 ·
-
Word(s) missing in article?Quizá libre de nuevo Un pull request para esta issue se cerró sin fusionarse. AbiertoChapter: events
Dificultad 1/5 Menos de una hora Aptitud para principiantes 70/100
jquery/learn.jquery.com#751 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 25/100
jquery/learn.jquery.com#814 · 1 comentario ·
-
Chapter: jquery-core help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 45/100
jquery/learn.jquery.com#799 ·
-
Chapter: plugins
Dificultad 2/5 1-3 horas Aptitud para principiantes 35/100
jquery/learn.jquery.com#796 ·
Todos los issues de jquery/learn.jquery.com
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
good first issue help wanted javascript up-for-grabs
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
andrewsiah/agentswarm-data-tasks#307 ·
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
coder/claudecode.nvim#588 ·
Los mantenedores suelen responder en 1 día
-
area: web tech debt
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
digitalbazaar/http-client#60 ·