Skip to content

Comments

docs: remove misleading link from "Don't over-optimize" section#720

Open
eduardbar wants to merge 1 commit intoryanmcdermott:masterfrom
eduardbar:fix/719-remove-misleading-link-dont-over-optimize
Open

docs: remove misleading link from "Don't over-optimize" section#720
eduardbar wants to merge 1 commit intoryanmcdermott:masterfrom
eduardbar:fix/719-remove-misleading-link-dont-over-optimize

Conversation

@eduardbar
Copy link

Summary

Removes a misleading external link from the "Don't over-optimize" section and replaces it with more actionable, timeless advice.

Problem

The section linked to github.com/petkaantonov/bluebird/wiki/Optimization-killers — a Bluebird Promise library wiki page about V8 optimization killers. This link is problematic because:

  1. It's outdated: The page describes V8 engine behaviors from several years ago that are no longer relevant to modern JavaScript runtimes.
  2. It's misleading: The source (a Promise library's wiki) is an unexpected and confusing place to look for JavaScript optimization guidance.
  3. It contradicts the section's message: The section advises developers not to over-optimize, but linking to optimization tricks encourages the opposite behavior.

Change

Replace the broken external link with a recommendation to use browser developer tools and performance profiling — the standard, modern approach to identifying real performance bottlenecks.

Before:

[There are good resources](https://github.com/petkaantonov/bluebird/wiki/Optimization-killers) for seeing where optimization is lacking.

After:

Use browser developer tools and performance profiling to identify real bottlenecks before optimizing.

Closes #719

The link to github.com/petkaantonov/bluebird/wiki/Optimization-killers
was misleading — it pointed to an outdated Bluebird Promise library
wiki page about V8 optimization killers that is no longer maintained
or accurate for modern JavaScript engines.

Replace with a general recommendation to use browser developer tools
and performance profiling to identify real bottlenecks, which is more
actionable and up-to-date advice.

Closes ryanmcdermott#719
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant