Lesson 7: JavaScript runtime foundations: Performance perspective

Concept Explanation

"JavaScript runtime foundations: Performance perspective" helps you think about speed and waste before code becomes messy or slow. The lesson does not aim at micro-optimizing everything. Instead, it teaches you to notice common habits that affect performance, such as repeated network calls, extra work inside loops, and unnecessary waiting in async code. You will look at a small async example, reason about what it costs to run, and make practical improvements that keep the code readable. By the end, you should be able to explain not just what the code does, but why one version is lighter and more efficient than another.

Where to Put the Code

1. Start with variables and inputs. Use browser or Node.js syntax clearly.
2. Add processing logic in the middle section.
3. Finish with output and quick validation.

Command Reference

• Run the example once, then identify which parts are network work and which parts are local processing.
• Add one small safeguard, such as a response check, without making the function harder to follow.
• Compare a wasteful version and a cleaner version, and explain where unnecessary work was removed.
• Describe one practical reason performance matters here, such as quicker feedback or fewer repeated requests.

Step-by-step Guide

1. Run the example and note what happens when the request succeeds.
2. Mark the line where asynchronous waiting begins and the line where the returned data is used.
3. Add one improvement that makes the flow more efficient or safer, such as checking the response before parsing.
4. Test one normal path and one failure path so you can see how the function behaves under both conditions.
5. Finish by summarizing what changed and why the updated version is a better fit for real projects.

Practice Exercises

• Update the example so it extracts only the names you need instead of passing around the full user objects everywhere.
• Create a second function that reuses the loaded data without making an extra fetch call.
• Rewrite the example with a slightly different structure and explain which version you would keep for long-term maintenance.

Coding Challenges

• Refactor a small async script that repeats the same request more than once so the data is fetched only once.
• Improve a slow-feeling example by removing one unnecessary step while keeping the result easy to understand.

Mini Practice Tasks

• Add one response check.
• Rename one function to better match what it returns.
• Write one sentence explaining where the main cost of this script comes from.