Why prototypes are needed in Javascript - Performance Analysis

Time Complexity: Why prototypes are needed

O(n)

Understanding Time Complexity

We want to understand why JavaScript uses prototypes and how this affects the speed of accessing properties and methods.

How does using prototypes change the work the program does when we create many objects?

Scenario Under Consideration

Analyze the time complexity of accessing a method on an object that uses a prototype.

function Person(name) {
  this.name = name;
}
Person.prototype.greet = function() {
  return `Hello, ${this.name}!`;
};

const alice = new Person('Alice');
console.log(alice.greet());
    

This code creates a person object and calls a method defined on its prototype.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Property lookup on the object and its prototype chain.
• How many times: Each method call requires checking the object and possibly its prototype once.

How Execution Grows With Input

When we create more objects, each method call still checks only a small chain of prototypes.

Input Size (n)	Approx. Operations
10	10 property lookups
100	100 property lookups
1000	1000 property lookups

Pattern observation: The work grows linearly with the number of method calls, but each lookup is quick because the prototype chain is short.

Final Time Complexity

Time Complexity: O(n)

This means if you call a method on n objects, the total work grows roughly in a straight line with n.

Common Mistake

[X] Wrong: "Using prototypes makes method calls instant with no work needed."

[OK] Correct: Each method call still needs to check the object and its prototype chain, so some work happens every time.

Interview Connect

Understanding prototypes helps you explain how JavaScript shares methods efficiently and why this matters for performance when many objects exist.

Self-Check

"What if methods were copied directly onto each object instead of using prototypes? How would the time complexity change?"

Practice

1. Why are prototypes needed in JavaScript?

easy

A. To prevent any changes to objects

B. To create new variables inside functions

C. To write code that runs faster on the server

D. To allow objects to share methods and properties efficiently

Solution

1. Step 1: Understand object sharing

   Prototypes let many objects share the same methods and properties without copying them.

2. Step 2: Recognize memory efficiency

   This sharing saves memory and makes code easier to maintain.

3. Final Answer:

   To allow objects to share methods and properties efficiently -> Option D

4. Quick Check:

   Prototypes = shared methods and properties [OK]

Hint: Prototypes share methods to save memory [OK]

Common Mistakes:

• Thinking prototypes create new variables
• Believing prototypes speed up server code
• Assuming prototypes prevent object changes

2. Which syntax correctly sets a method on a prototype in JavaScript?

easy

A. MyObject.myMethod = function() { return 1; };

B. MyObject.prototype.myMethod = function() { return 1; };

C. prototype.MyObject.myMethod = function() { return 1; };

D. MyObject->prototype->myMethod = function() { return 1; };

Solution

1. Step 1: Identify correct prototype syntax

   In JavaScript, the prototype property is accessed as MyObject.prototype.

2. Step 2: Confirm method assignment

   Assigning a function to MyObject.prototype.myMethod adds it to the prototype.

3. Final Answer:

   MyObject.prototype.myMethod = function() { return 1; }; -> Option B

4. Quick Check:

   Correct prototype syntax = MyObject.prototype.myMethod = function() { return 1; }; [OK]

Hint: Use .prototype to add methods to objects [OK]

Common Mistakes:

• Using MyObject.myMethod instead of prototype
• Writing prototype.MyObject instead of MyObject.prototype
• Using arrows (->) instead of dots (.)

3. What will be the output of this code?

function Person(name) { this.name = name; }
Person.prototype.greet = function() { return 'Hi, ' + this.name; };
const p = new Person('Anna');
console.log(p.greet());

medium

A. 'Hi, Anna'

B. ReferenceError: name is not defined

C. TypeError: p.greet is not a function

D. 'Hi, undefined'

Solution

1. Step 1: Understand constructor and prototype method

   The Person function sets this.name to 'Anna'. The greet method is on Person.prototype.

2. Step 2: Call greet on instance

   Calling p.greet() finds greet on prototype and returns 'Hi, Anna'.

3. Final Answer:

   'Hi, Anna' -> Option A

4. Quick Check:

   Prototype method returns greeting with name [OK]

Hint: Prototype methods are accessible on instances [OK]

Common Mistakes:

• Expecting greet to be undefined
• Confusing instance properties with prototype
• Thinking greet is not a function

4. Find the error in this code that tries to add a method to a prototype:

function Car() {}
Car.prototype = {
  start: function() { return 'Car started'; }
};
const c = new Car();
console.log(c.start());

medium

A. The prototype is overwritten, losing the constructor reference

B. The start method is not a function

C. Car is not defined before use

D. Cannot assign an object to prototype

Solution

1. Step 1: Check prototype assignment

   Assigning an object to Car.prototype replaces the original prototype and removes the constructor link.

2. Step 2: Understand consequence

   This can cause issues if code relies on constructor property or inheritance chain.

3. Final Answer:

   The prototype is overwritten, losing the constructor reference -> Option A

4. Quick Check:

   Overwriting prototype removes constructor [OK]

Hint: Avoid overwriting prototype object directly [OK]

Common Mistakes:

• Thinking start is not a function
• Believing Car is undefined
• Assuming prototype cannot be an object

5. You want to add a method describe to all objects created by function Animal(type) without copying it to each instance. How should you do it?

hard

A. Add describe method to each instance manually after creation

B. Add describe method inside Animal function using this.describe

C. Add describe method to Animal.prototype

D. Add describe method to Object.prototype

Solution

1. Step 1: Understand method sharing

   Adding describe to Animal.prototype shares it with all instances without copying.

2. Step 2: Avoid inefficient or unsafe options

   Adding inside constructor copies method per instance; adding to Object.prototype affects all objects globally.

3. Final Answer:

   Add describe method to Animal.prototype -> Option C

4. Quick Check:

   Use prototype to share methods efficiently [OK]

Hint: Put shared methods on constructor's prototype [OK]

Common Mistakes:

• Adding methods inside constructor wastes memory
• Modifying Object.prototype can cause bugs
• Manually adding methods to each instance is inefficient