Why TypeScript over JavaScript - Performance Analysis

Time Complexity: Why TypeScript over JavaScript

O(n)

Understanding Time Complexity

We want to see how choosing TypeScript instead of JavaScript affects the time it takes for code to run.

Does adding TypeScript's features make programs slower or faster as they grow?

Scenario Under Consideration

Analyze the time complexity of this simple TypeScript function compared to JavaScript.

function sumArray(numbers: number[]): number {
  let total = 0;
  for (const num of numbers) {
    total += num;
  }
  return total;
}

This function adds all numbers in an array and returns the total.

Identify Repeating Operations

Look at what repeats as the input grows.

• Primary operation: Looping through each number in the array.
• How many times: Once for every item in the input array.

How Execution Grows With Input

As the array gets bigger, the function does more additions.

Input Size (n)	Approx. Operations
10	10 additions
100	100 additions
1000	1000 additions

Pattern observation: The work grows directly with the number of items.

Final Time Complexity

Time Complexity: O(n)

This means the time to finish grows in a straight line with the input size.

Common Mistake

[X] Wrong: "TypeScript makes the code run slower because it adds extra checks at runtime."

[OK] Correct: TypeScript checks happen before running the code, so the running speed is the same as JavaScript.

Interview Connect

Understanding how TypeScript affects code speed helps you explain your choices clearly and shows you know how tools impact performance.

Self-Check

"What if we added complex type checks inside the function at runtime? How would the time complexity change?"

Practice

1. Why do many developers choose TypeScript over plain JavaScript?

easy

A. Because TypeScript uses fewer lines of code than JavaScript

B. Because TypeScript runs faster in browsers than JavaScript

C. Because TypeScript does not require any compilation

D. Because TypeScript helps catch errors before running the code

Solution

1. Step 1: Understand TypeScript's main benefit

   TypeScript adds types to JavaScript, which helps find mistakes early, before running the code.

2. Step 2: Compare options with this benefit

   Only Because TypeScript helps catch errors before running the code mentions catching errors early, which is the key reason developers prefer TypeScript.

3. Final Answer:

   Because TypeScript helps catch errors before running the code -> Option D

4. Quick Check:

   Type safety = Catch errors early [OK]

Hint: Remember: TypeScript finds bugs before running code [OK]

Common Mistakes:

• Thinking TypeScript runs faster in browsers
• Believing TypeScript needs no compilation
• Assuming TypeScript always reduces code length

2. Which of the following is the correct way to declare a typed variable in TypeScript?

easy

A. let age = number 25;

B. let age: number = 25;

C. let age = 25: number;

D. let age number = 25;

Solution

1. Step 1: Recall TypeScript variable syntax

   In TypeScript, the type comes after the variable name, separated by a colon, like let varName: type.

2. Step 2: Check each option's syntax

   Only let age: number = 25; uses the correct syntax: let age: number = 25;. Others have misplaced or missing colons.

3. Final Answer:

   let age: number = 25; -> Option B

4. Quick Check:

   Variable: type = value [OK]

Hint: Type comes after variable name with colon [OK]

Common Mistakes:

• Placing type before variable name
• Using colon after value instead of after variable
• Omitting colon between variable and type

3. What will be the output of this TypeScript code after compilation and running in JavaScript?

function greet(name: string) {
  return `Hello, ${name.toUpperCase()}!`;
}
console.log(greet("world"));

medium

A. Hello, WORLD!

B. Error: name.toUpperCase is not a function

C. HELLO, WORLD!

D. Hello, world!

Solution

1. Step 1: Understand the function behavior

   The function takes a string and returns "Hello, " plus the uppercase version of the name plus "!".

2. Step 2: Apply the function to input "world"

   Calling name.toUpperCase() on "world" returns "WORLD", so the output is "Hello, WORLD!".

3. Final Answer:

   Hello, WORLD! -> Option A

4. Quick Check:

   toUpperCase("world") = "WORLD" [OK]

Hint: Remember string methods like toUpperCase() work on strings [OK]

Common Mistakes:

• Ignoring toUpperCase effect
• Assuming output is all uppercase
• Expecting runtime error due to types

4. Identify the error in this TypeScript code snippet:

function add(a: number, b: number) {
  return a + b;
}

console.log(add(5, "10"));

medium

A. Type error: second argument should be a number, not a string

B. No error, outputs 15

C. Syntax error: missing return type

D. Runtime error: cannot add number and string

Solution

1. Step 1: Check function parameter types

   The function expects both parameters to be numbers.

2. Step 2: Analyze the call with arguments (5, "10")

   The second argument is a string, which conflicts with the expected number type, causing a TypeScript type error before running.

3. Final Answer:

   Type error: second argument should be a number, not a string -> Option A

4. Quick Check:

   Type mismatch argument = Error [OK]

Hint: Check argument types match parameter types [OK]

Common Mistakes:

• Assuming implicit string to number conversion
• Thinking missing return type causes error
• Expecting runtime error instead of compile-time

5. You want to create a function in TypeScript that accepts either a string or a number and returns its string length or digit count. Which approach best uses TypeScript's features to handle this safely?

hard

A. Declare two separate functions, one for string and one for number

B. Declare the parameter as type any and convert it to string inside

C. Use a union type for the parameter and check its type inside the function

D. Use JavaScript without types to avoid complexity

Solution

1. Step 1: Understand TypeScript union types

   Union types allow a variable to be one of several types, e.g., string | number.

2. Step 2: Use type checking inside function

   Inside the function, use typeof to check if the input is string or number, then handle accordingly. This keeps type safety and clarity.

3. Final Answer:

   Use a union type for the parameter and check its type inside the function -> Option C

4. Quick Check:

   Union types + type guards = safe handling [OK]

Hint: Use union types and type checks for multiple input types [OK]

Common Mistakes:

• Using any type loses type safety
• Creating duplicate functions unnecessarily
• Avoiding TypeScript features by using plain JavaScript