jprdonnelly/freeCodeCamp
1
0
Fork 0
mirror of https://github.com/freeCodeCamp/freeCodeCamp.git synced 2026-04-14 07:00:51 -04:00
Code Issues Projects Releases Wiki Activity

fix(curriculum): clarify performance.now() precision and update quiz answer (#63694)

Browse Source
This commit is contained in:
𝙠𝙚𝙣𝙖𝙞𝙡
2025-11-10 21:49:58 +05:30
committed by GitHub
parent 2bbb66a854
commit 13ec0d5a90
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
curriculum/challenges/english/blocks/lecture-understanding-performance-in-web-applications/67d2f7cf63fafe7d20270498.md
View File

@@ -35,7 +35,7 @@ const end = performance.now();
console.log(`Execution time: ${end - start}ms`);
```
This is more accurate than using `Date.now()` because it measures time in microseconds, avoiding clock drift issues. You can use it to track script execution time, event response delays and animation performance.
This is more accurate than using `Date.now()` because it measures time in milliseconds with microsecond precision, avoiding clock drift issues. You can use it to track script execution time, event response delays, and animation performance.
Next, the Performance Timing API.
@@ -97,7 +97,7 @@ What is the main advantage of using `performance.now()` over `Date.now()`?
## --answers--
It's more accurate and measures time in microseconds.
It's more accurate and measures time in milliseconds with microsecond precision.
---