Why TypeScript is so nice to use

TypeScript helps developers write more robust and maintainable code compared to plain JavaScript by providing optional static type checking, better IDE support, and improved error detection during development. This means that TypeScript can catch errors at compile-time, before code is even executed, rather than having to wait until runtime to catch errors.

Here’s a simple example that demonstrates how TypeScript can help catch a potential error:

JavaScript code:

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

const result = add("2", "3"); // result will be "23"

TypeScript code:

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

const result = add("2", "3"); // TypeScript error: Argument of type 'string' is not assignable to parameter of type 'number'.

In the JavaScript code, the add function takes two arguments, but the types of those arguments are not specified. As a result, the function can be called with any type of argument, which can lead to unexpected behavior. For example, in the example above, the add the function is called with two strings, which are concatenated instead of added, resulting in the string "23".

In contrast, in the TypeScript code, the types of the arguments are specified as number, and when the function is called with two strings, the TypeScript compiler detects the type mismatch and throws a compile-time error. This helps catch the error early in the development process and makes it easier to maintain the code in the long run.